Guangya Liu created MESOS-5611:
----------------------------------
Summary: Error message is not clear when create docker volume with
absolute path
Key: MESOS-5611
URL: https://issues.apache.org/jira/browse/MESOS-5611
Project: Mesos
Issue Type: Bug
Components: isolation
Reporter: Guangya Liu
Assignee: Guangya Liu
When I was doing some test with mesos-execute to mount some volumes, I found
that the error message is not clear when I was using absolute path for a
container without rootfs.
{code}
root@mesos002:~/src/mesos/m2/mesos/build# ./src/mesos-execute
--master=192.168.56.12:5050 --command="sleep 100000" --name=test
--volumes=/root/test/volume4.json
WARNING: Logging before InitGoogleLogging() is written to STDERR
W0614 09:21:25.100939 28209 parse.hpp:115] Specifying an absolute filename to
read a command line option out of without using 'file:// is deprecated and will
be removed in a future release. Simply adding 'file://' to the beginning of the
path should eliminate this warning.
I0614 09:21:25.104532 28209 scheduler.cpp:187] Version: 1.0.0
I0614 09:21:25.106834 28231 scheduler.cpp:471] New master detected at
[email protected]:5050
Subscribed with ID '57cda92a-b703-435a-94f0-28e88746f8b5-0000'
Submitted task 'test' to agent '57cda92a-b703-435a-94f0-28e88746f8b5-S0'
Received status update TASK_FAILED for task 'test'
message: 'Failed to launch container: Absolute container path does not exist;
Container destroyed while preparing isolators'
{code}
The error message {{Absolute container path does not exist;}} should include
the absolute path.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
