How to set docker run arguments on marathon spec

I have been using docker to run images along with some options like:

docker run --net host --oom-kill-disable -d -p <port>:<port> image

How do I set values like –oom-kill-disable on marathon?

  • jar file with arguments in docker
  • Jenkins and running rake tasks
  • How to keep a service running on a Docker container
  • register docker container to host network dns
  • docker-composer.yml not work properly
  • Using zookeeper for service discovery of mesos slaves running docker
  • where does docker attach volume on host machine when its not specified?
  • Docker, how to deal with ssh keys, known_hosts and authorized_keys
  • how to cache build env in docker-compose
  • How can I set an overlay network within docker compose
  • Docker jenkins container, host key verification failed
  • How to set a time limit for a Kubernetes job?
  • 2 Solutions collect form web for “How to set docker run arguments on marathon spec”

    I’m not quite sure if you can pass an empty value in this case, but you could go with something like this:

    "container": {
        "type": "DOCKER",
        "docker": {
            "network": "HOST",
            "image": "your/image",
            "parameters": [
                { "key": "oom-kill-disable", "value": "" }

    You may read a little bit more here in “Privileged Mode and Arbitrary Docker Options” section.

    It is required for docker containers in their marathon spec to specify a boolean value for oom-kill-disable flag for executor to run properly.

    So the spec would include:

    "parameters": [
                { "key": "oom-kill-disable", "value": "true" }
    Docker will be the best open platform for developers and sysadmins to build, ship, and run distributed applications.