Description
Hello All,
I've been using Mesos for my work and it seems like to me that a recent commit to the Mesos source (https://github.com/apache/mesos/commit/b0e7cb1483fa3b7efa46bd82a89ed4dabfc5263a) that aims to parse Env. info from the pulled docker images made it impossible for me to use my Docker images in my private Docker registry. I used these images for a long period of time, but they became unusable in the new version of Mesos. I face no problem pulling and running public images from Docker Hub.
Error message:
"Failed to launch container: Unable to create image: Unexpected Env format for 'ContainerConfig.Env'"
I attempted to use my images with other versions of Marathon and Docker, but the error message is the same. I also tried multiple ways of authenticating my private registry, but to no awail.
Additional info:
- I launch these images from Marathon, but I'm pretty certain that the problem comes from Mesos
- I'm using the playa-mesos VM for development and I provisioned it several days ago.
Attachments
Issue Links
- is related to
-
MESOS-4587 Docker environment variables must be able to contain the equal sign
-
- Resolved
-