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?

  • CoreOS : when pulling large docker image of size greater than 4 GB
  • Docker container: lsmod not found
  • Accesing Spring-Boot WebApplication running in Docker Container
  • send keys to terminal
  • What's benefit of docker's image layer?
  • Docker: how to set up file ownership in a data-only container?
  • How to create a docker image for php and node?
  • After update, can't make requests in flask running in docker but can ping
  • error: repository [dockerimage] not found: does not exist or no pull access-docker
  • Using remote byebug instance with docker-compose
  • Jetty Docker container running spring application unable to connect to mysql running outside docker container
  • Java Spring will not talk to Consul when run as a Docker container
  • 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.