Closed geoffroyjabouley closed 8 years ago
Hi @geoffroyjabouley, thanks for reporting this. It seems to be a duplicate of https://github.com/mesosphere/marathon/issues/2373. Reopen if you disagree.
Yep just found it, thanks for having closing this duplicate.
Well, your bug report was really good, so thanks for that :) @geoffroyjabouley
Hello
my setup is the following:
I have a running Marathon application created using the attached json, which works fine.
The docker image domain/backoffice has an entrypoint declaration, thus no "cmd" field is needed in the json.
A
docker ps
command on the host running the image returns (truncated):docker inspect 556680ec25fc
returns (truncated):I am trying to update this app using the Marathon UI. For example only change the memory field to 256MB.
Whenever i make the change and submit the new configuration, the task is not able to start anymore.
It seems that Marathon overrides the image entry point with /bin/sh and then use an empty cmd field in the configuration, so the docker container starts and immediately exits without error.
Some information for debugging:
A
docker ps
command on the host containing the container with updated Marathon configuration (truncated):docker inspect b376477a706a
returns (truncated):Marathon log when updating the configuration