[
https://issues.apache.org/jira/browse/MESOS-5123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Greg Mann updated MESOS-5123:
-----------------------------
Fix Version/s: 0.29.0
> Docker task may fail if path to agent work_dir is relative.
> ------------------------------------------------------------
>
> Key: MESOS-5123
> URL: https://issues.apache.org/jira/browse/MESOS-5123
> Project: Mesos
> Issue Type: Improvement
> Components: docker
> Affects Versions: 0.28.0, 0.29.0
> Reporter: Alexander Rukletsov
> Labels: docker, documentation, mesosphere
> Fix For: 0.29.0
>
>
> When a local folder for agent’s {{\-\-work_dir}} is specified (e.g.,
> {{\-\-work_dir=w/s}}) docker complains that there are forbidden symbols in a
> *local* volume name. Specifying an absolute path (e.g.,
> {{\-\-work_dir=/tmp}}) solves the problem.
> Docker error observed:
> {noformat}
> docker: Error response from daemon: create
> w/s/slaves/33b8fe47-e9e0-468a-83a6-98c1e3537e59-S1/frameworks/33b8fe47-e9e0-468a-83a6-98c1e3537e59-0001/executors/docker-test/runs/3cc5cb04-d0a9-490e-94d5-d446b66c97cc:
> volume name invalid:
> "w/s/slaves/33b8fe47-e9e0-468a-83a6-98c1e3537e59-S1/frameworks/33b8fe47-e9e0-468a-83a6-98c1e3537e59-0001/executors/docker-test/runs/3cc5cb04-d0a9-490e-94d5-d446b66c97cc"
> includes invalid characters for a local volume name, only
> "[a-zA-Z0-9][a-zA-Z0-9_.-]" are allowed.
> {noformat}
> First off, it is not obvious that Mesos always creates a volume for the
> sandbox. We may want to document it.
> Second, it's hard to understand that local {{work_dir}} can trigger forbidden
> symbols error in docker. Does it make sense to check it during agent launch
> if docker containerizer is enabled? Or reject docker tasks during task
> validation?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
