Unable to launch container from Marathon without privileged option about deimos HOT 7 CLOSED

Hi,

try

{
  "container": {
    "image": "docker:///libmesos/ubuntu",
    "options": ["--privileged=false"]
  },
  "id": "ubuntu",
  "instances": "1",
  "cpus": ".5",
  "mem": "300",
  "uris": [ ],
  "cmd": "sleep 500"
}

Mike

from deimos.

That worked, and --privileged=true worked, but I don't have the privileged option at all, the container never starts up.

from deimos.

Wow, never seen this one before. Is Deimos configured to use the UNIX socket or the TCP socket to talk to Docker?

from deimos.

I've removed any special startup configuration on docker, so by default, I believe it just listens on the socket and not TCP. I'll keep playing around with it to see if I can figure out what's going on.

I installed mesos from the mesosphere APT repo and installed deimos 0.3.2 from pip.

from deimos.

I've put up some files I'm testing with in https://gist.github.com/jplock/b80a3979d590b041fc4c

I'm able to start up ubuntu-true.json and ubuntu-false.json fine, but ubuntu-missing.json never starts up.

I'm launching the by executing:

curl -X POST -H "Content-Type: application/json" -d @ubuntu-true.json localhost:8080/v2/apps

from deimos.

This appears to be a serialization bug in Marathon. The following JSON works:

{
  "container": {
    "image": "docker:///libmesos/ubuntu",
    "options": []
  },
  "id": "ubuntu-missing",
  "instances": "1",
  "cpus": ".5",
  "mem": "300",
  "uris": [ ],
  "cmd": "sleep 500"
}

from deimos.

Is there a followup bug fix in Marathon? or somewhere I can track this issue in Marathon?

from deimos.