Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
0.20.0
-
ubuntu (mesosphere vangrant vm)
-
Mesosphere Q4 Sprint 1 10/31
Description
I created and launched a container successfully in chronos, but when mesos ran the docker container, docker did not accept the volumes setting due to the colon in the executor id (-v option). Here is the executor id, which is valid: ct:1411670160000:0:lldocker.
In mesos, there will be a fix to avoid using the host directory by use of a simlink and mapping. However, ideally docker will fix this issue. They should accept executor ids with colons as the format is valid.
Here is the error log:
Error: One iContainer '8fdb0cd7-86f8-4bc9-bd1b-d36f86663bb3' for executor 'ct:1411670160000:0:lldocker' of framework '20140925-174859-16842879-5050-1573-0000' failed to start: Failed to 'docker run -d -c 512 -m 536870912 -e mesos_task_id=ct:1411670160000:0:lldocker -e CHRONOS_JOB_OWNER= -e MESOS_SANDBOX=/mnt/mesos/sandbox -v /tmp/mesos/slaves/20140925-181954-16842879-5050-1560-0/frameworks/20140925-174859-16842879-5050-1573-0000/executors/ct:1411670160000:0:lldocker/runs/8fdb0cd7-86f8-4bc9-bd1b-d36f86663bb3:/mnt/mesos/sandbox --net host --entrypoint /bin/sh --name mesos-8fdb0cd7-86f8-4bc9-bd1b-d36f86663bb3 libmesos/ubuntu -c while sleep 10; do date =u %T; done': exit status = exited with status 2 stderr = invalid value "/tmp/mesos/slaves/20140925-181954-16842879-5050-1560-0/frameworks/20140925-174859-16842879-5050-1573-0000/executors/ct:1411670160000:0:lldocker/runs/8fdb0cd7-86f8-4bc9-bd1b-d36f86663bb3:/mnt/mesos/sandbox" for flag -v: bad format for volumes: /tmp/mesos/slaves/20140925-181954-16842879-5050-1560-0/frameworks/20140925-174859-16842879-5050-1573-0000/executors/ct:1411670160000:0:lldocker/runs/8fdb0cd7-86f8-4bc9-bd1b-d36f86663bb3:/mnt/mesos/sandbox
Attachments
Issue Links
- relates to
-
MESOS-7450 Docker containerizer will leak dangling symlinks if restarted with a colon in the sandbox path
- Open
- links to