Generic way of passing docker parameters

[strzelecki-maciek]

On top of #484 , wouldnt it be better if You copied the way Marathon is handling docker parameters passing?

This gives much more flexibility into passing parameters, especially:

 "parameters": [
            { "key": "a-docker-option", "value": "xxx" },
            { "key": "b-docker-option", "value": "yyy" }
        ]

taken from: https://mesosphere.github.io/marathon/docs/rest-api.html#post-v2-apps

"container": {
"type": "DOCKER",
"docker": {
"image": "group/image",
"network": "BRIDGE",
"portMappings": [
{
"containerPort": 8080,
"hostPort": 0,
"servicePort": 9000,
"protocol": "tcp"
},
{
"containerPort": 161,
"hostPort": 0,
"protocol": "udp"
}
],
"privileged": false,
"parameters": [
{ "key": "a-docker-option", "value": "xxx" },
{ "key": "b-docker-option", "value": "yyy" }
]
},
"volumes": [
{
"containerPath": "/etc/a",
"hostPath": "/var/data/a",
"mode": "RO"
},
{
"containerPath": "/etc/b",
"hostPath": "/var/data/b",
"mode": "RW"
}
]
},

[bobrik]

+1 for this feature, logging could benefit from this.

[yanglei99]

I would also like the support of passing "env" to Docker containers as what Marathon does today. e.g.
"env": {
"LD_LIBRARY_PATH": "/usr/local/lib/myLib"
},

[strzelecki-maciek]

closing, as Feature/docker params #538 was merged