Balint Kubik created MESOS-4594:
-----------------------------------
Summary: Parsing 'Env' in docker images renders private Docker
registries unusable
Key: MESOS-4594
URL: https://issues.apache.org/jira/browse/MESOS-4594
Project: Mesos
Issue Type: Epic
Components: docker
Affects Versions: 0.27.0
Reporter: Balint Kubik
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.
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.
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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
