Marathon: Host-to-container volume mapping in Marathon 1.1

Created on 19 Apr 2016  路  6Comments  路  Source: mesosphere/marathon

Since upgrading to Marathon 1.1, I don't see an option in GUI to map host path to Docker container path (as usually submitted with docker --volume flag).

Since my applications are still running, I assume that json way still works:

...
  "volumes": [
    {
      "containerPath": "/data/hadoop",
      "hostPath": "/opt/data/hadoop",
      "mode": "RW"
   }
 ]
...

Is there a plan to discontinue support for volume mappings?

GUI volume config:
screen shot 2016-04-19 at 13 07 20

If submitted via JSON:
screen shot 2016-04-19 at 13 07 44

Relevant? :-)
workflow

Most helpful comment

Show the volume widgets, but make them disabled with a tooltip "only available for Docker containers".

All 6 comments

Hi @liquid-sky

we didn't remove the spacebar heating 馃槈 simply make sure you specify a docker image first in the Docker Container settings to access the docker volume settings.

@leemunroe we should consider adding a tooltip or some sort of information in the Volumes section mentioning that you need to specify a docker image first to have access to the docker volumes.

Alternatively we could simply "grey out" the Docker settings until an image is set.

Show the volume widgets, but make them disabled with a tooltip "only available for Docker containers".

Ahh, just noticed that the section appears when docker image name is entered. Thanks, folks!

@sttts solution sounds good. Something like "First configure your Docker container" and link to the section.

Note: This issue has been migrated to https://jira.mesosphere.com/browse/MARATHON-1884. For more information see https://groups.google.com/forum/#!topic/marathon-framework/khtvf-ifnp8.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

timcharper picture timcharper  路  4Comments

balopat picture balopat  路  5Comments

ssk2 picture ssk2  路  14Comments

robertd picture robertd  路  5Comments

bydga picture bydga  路  8Comments