Andrii, you might also be interested in the new --executor_environment_variables flag on the slave. See http://mesos.apache.org/documentation/latest/configuration/ I'm not sure if this override occurs before the docker run command.
On Mon, Aug 3, 2015 at 8:51 AM, Timothy Chen <[email protected]> wrote: > Hi Andrii, > > We never intend to pick up local OS environment to be passed into > containerizer, as we want to make sure all environment variables are > intentionally specifies from the framework for the task. > > Does that docker.conf setting generate a new docker.conf file or? > > Tim > > > > > On Aug 3, 2015, at 2:51 AM, Andrii Loshkovskyi <[email protected]> > wrote: > > > > Hello, > > > > I was able to change DOCKER_HOST in Mesos 0.22.1 but with upgrade to > Mesos 0.23 I'm no longer able to do that. > > > > I override the systemd unit file this way: > > > > cat /etc/systemd/system/mesos-slave.service.d/docker.conf > > [Service] > > Environment="DOCKER_HOST=localhost:2377" > > > > cat /etc/mesos-slave/containerizers > > docker,mesos > > > > This doesn't work in the latest Mesos. I use CentOS 7, Docker 1.6.2. > > From the changelog I see that there were a lot of changes to containers > network isolation in Mesos, maybe it's somehow related. > > I have checked the containeraizer code, but not able to identify the > issue. > > > > I would really appreciate if someone advises me on this issue. > > > > Thank you. > > > > -- > > Kind regards, > > Andrii Loshkovskyi >
