[
https://issues.apache.org/jira/browse/MESOS-4446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15114294#comment-15114294
]
Guangya Liu commented on MESOS-4446:
------------------------------------
I did not have a strong reason for this but only want to make life easier for
end user. I think that many end users tend to use the Marathon Json template
following docker API, that's why [~gena01] filed this issue as he did not found
the parameter.
For Volume, with parameters, we can use it as
{code}
"parameters": [
{ "key": "volume", "value": "/opt:/opt" }
{code}
For network
{code}
"parameters": [
{ "key": "net", "value": "host" }
{code}
If that is the way, then all of the docker API requested parameters can use
this {{parameters}} field to transfer those parameters which dose not seems
reasonable...
I think that you can find a shepherd to have some discussion for this. thanks.
> Please add an ability to set Docker labels based on TaskStatus labels
> ---------------------------------------------------------------------
>
> Key: MESOS-4446
> URL: https://issues.apache.org/jira/browse/MESOS-4446
> Project: Mesos
> Issue Type: Story
> Components: docker
> Reporter: Gennady Feldman
>
> So looks like MESOS-3076 added support for Labels to TaskStatus. Would it be
> possible to pass those onto the docker container?
> This would really help with doing "docker inspect" on the mesos-slave nodes
> as well as allow us to better collect docker metrics about the
> tasks/containers that are currently running on the slave.
> docker supports labels out of the box. See here:
> https://docs.docker.com/engine/userguide/labels-custom-metadata/
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
