elemakil
commented
5 years ago I have connected into one of the nodes using ssh. This allows me to manually execute docker info:
$ sudo docker info | grep "Docker Root Dir"
WARNING: API is accessible on http://127.0.0.1:2375 without encryption.
Access to the remote API is equivalent to root access on the host. Refer
to the 'Docker daemon attack surface' section in the documentation for
more information: https://docs.docker.com/engine/security/security/#docker-daemon-attack-surface
WARNING: No swap limit support
Docker Root Dir: /mnt/dockerI believe the leading space in front of "Docker Root Dir" is the source of the problems. However, I have no clue as to its origin.
alfpark
JadenLy
canoas
Problem Description
I have been using Azure Batch Shipyard with VMs of type STANDARD_NC6 succesfully for a while. Usually, I create a pool, submit some jobs (with several tasks) and kill the pool again, all over the course of at most a couple of days.
As of today, when creating the pool and submitting a job, all nodes enter the "starttaskfailed" state. I have deleted and recreated the pool and job several times. Using the Azure Batch Explorer I have checked the node startup logs and find the following text at the bottom of
stdout.txt:This seems to originate from
shipyard_nodeprep.shline 730-737:It looks like the
cutcommand does not properly extract the "Docker Root Dir" from the output ofdocker info(note that$rootdir = "Dir:"!).Batch Shipyard Version
3.7.0
Steps to Reproduce
Create pool, then create job.
Expected Results
The pool gets created and the job + tasks start properly.
Actual Results
All nodes in the pool get stuck in "starttaskfailed"
Redacted Configuration
pool:
Additional Logs
Header part from
stdout.txt:Additonal Comments