[jira] [Commented] (MESOS-6340) Set HOME for Mesos tasks
[
https://issues.apache.org/jira/browse/MESOS-6340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16408447#comment-16408447
]
michael beisiegel commented on MESOS-6340:
--
I'm using a docker image based on ubuntu:16.04 with vi installed. After 'dcos
task exec ...' into the container I get the following messages.
*on start vi*
{color:#205081}Cannot execute shell /usr/bin/bash{color}
{color:#205081}E79: Cannot expand wildcards{color}
{color:#205081}Cannot execute shell /usr/bin/bash{color}
{color:#205081}E79: Cannot expand wildcards{color}
*on close vi*
{color:#205081}E138: Can't write viminfo file $HOME/.viminfo! {color}
{color:#205081}Press ENTER or type command to continue{color}
The HOME env var is not set. Once I set HOME to /root or $MESOS_SANDBOX the
messages are gone.
> Set HOME for Mesos tasks
>
>
> Key: MESOS-6340
> URL: https://issues.apache.org/jira/browse/MESOS-6340
> Project: Mesos
> Issue Type: Bug
> Components: agent, containerization
>Reporter: Cody Maloney
>Priority: Major
> Labels: containerizer
>
> Quite a few programs assume {{$HOME}} points to a user-editable data file
> directory.
> One example is PYTHON, which tries to look up $HOME to find user-installed
> pacakges, and if that fails it tries to look up the user in the passwd
> database which often goes badly (The container is running under the `nobody`
> user):
> {code}
> if i == 1:
> if 'HOME' not in os.environ:
> import pwd
> userhome = pwd.getpwuid(os.getuid()).pw_dir
> else:
> userhome = os.environ['HOME']
> {code}
> Just setting HOME by default to WORK_DIR would enable more software to work
> correctly out of the box. Software which needs to specialize / change it (or
> schedulers with specific preferences), should still be able to set it
> arbitrarily and anything a scheduler explicitly sets should overwrite the
> default value of $WORK_DIR
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MESOS-7652) docker image not working with universal containerizer
[
https://issues.apache.org/jira/browse/MESOS-7652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16084344#comment-16084344
]
michael beisiegel commented on MESOS-7652:
--
Researched this some more, found the following spot in the mesos code.
https://github.com/apache/mesos/blob/35dd2b600b8af0204d03c4ee5348a1a6672b136c/src/slave/containerizer/mesos/launch.cpp
line 567
The Dockerfile reference says for WORKDIR the following.
"
...
If the WORKDIR doesn’t exist, it will be created even if it’s not used in any
subsequent Dockerfile instruction.
"
Looks like the create is missing in the code if it does not exist.
> docker image not working with universal containerizer
> -
>
> Key: MESOS-7652
> URL: https://issues.apache.org/jira/browse/MESOS-7652
> Project: Mesos
> Issue Type: Bug
> Components: containerization
>Affects Versions: 1.2.1
>Reporter: michael beisiegel
>Priority: Minor
>
> hello,
> used the following docker image recently
> quay.io/spinnaker/front50:master
> https://quay.io/repository/spinnaker/front50
> Here the link to the Dockerfile
> https://github.com/spinnaker/front50/blob/master/Dockerfile
> and here the source
> {color:blue}FROM java:8
> MAINTAINER delivery-engineer...@netflix.com
> COPY . workdir/
> WORKDIR workdir
> RUN GRADLE_USER_HOME=cache ./gradlew buildDeb -x test && \
> dpkg -i ./front50-web/build/distributions/*.deb && \
> cd .. && \
> rm -rf workdir
> CMD ["/opt/front50/bin/front50"]{color}
> The image works fine with the docker containerizer, but the universal
> containerizer shows the following in stderr.
> "Failed to chdir into current working directory '/workdir': No such file or
> directory"
> The problem comes from the fact that the Dockerfile creates a workdir but
> then later removes the created dir as part of a RUN. The docker containerizer
> has no problem with it if you do
> docker run -ti --rm quay.io/spinnaker/front50:master bash
> you get into the working dir, but the universal containerizer fails with the
> error.
> thanks for your help,
> Michael
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (MESOS-7652) docker image not working with universal containerizer
[
https://issues.apache.org/jira/browse/MESOS-7652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
michael beisiegel updated MESOS-7652:
-
Description:
hello,
used the following docker image recently
quay.io/spinnaker/front50:master
https://quay.io/repository/spinnaker/front50
Here the link to the Dockerfile
https://github.com/spinnaker/front50/blob/master/Dockerfile
and here the source
{color:blue}FROM java:8
MAINTAINER delivery-engineer...@netflix.com
COPY . workdir/
WORKDIR workdir
RUN GRADLE_USER_HOME=cache ./gradlew buildDeb -x test && \
dpkg -i ./front50-web/build/distributions/*.deb && \
cd .. && \
rm -rf workdir
CMD ["/opt/front50/bin/front50"]{color}
The image works fine with the docker containerizer, but the universal
containerizer shows the following in stderr.
"Failed to chdir into current working directory '/workdir': No such file or
directory"
The problem comes from the fact that the Dockerfile creates a workdir but then
later removes the created dir as part of a RUN. The docker containerizer has no
problem with it if you do
docker run -ti --rm quay.io/spinnaker/front50:master bash
you get into the working dir, but the universal containerizer fails with the
error.
thanks for your help,
Michael
was:
hello,
used the following docker image recently
quay.io/spinnaker/front50:master
https://quay.io/repository/spinnaker/front50
Here the link to the Dockerfile
https://github.com/spinnaker/front50/blob/master/Dockerfile
The image works fine with the docker containerizer, but the universal
containerizer shows the following in stderr.
"Failed to chdir into current working directory '/workdir': No such file or
directory"
The problem comes from the fact that the Dockerfile creates a workdir but then
later removes the created dir as part of a RUN. The docker containerizer has no
problem with it if you do
docker run -ti --rm quay.io/spinnaker/front50:master bash
you get into the working dir, but the universal containerizer fails with the
error.
thanks for your help,
Michael
> docker image not working with universal containerizer
> -
>
> Key: MESOS-7652
> URL: https://issues.apache.org/jira/browse/MESOS-7652
> Project: Mesos
> Issue Type: Bug
> Components: containerization
>Affects Versions: 1.2.1
>Reporter: michael beisiegel
>Priority: Minor
>
> hello,
> used the following docker image recently
> quay.io/spinnaker/front50:master
> https://quay.io/repository/spinnaker/front50
> Here the link to the Dockerfile
> https://github.com/spinnaker/front50/blob/master/Dockerfile
> and here the source
> {color:blue}FROM java:8
> MAINTAINER delivery-engineer...@netflix.com
> COPY . workdir/
> WORKDIR workdir
> RUN GRADLE_USER_HOME=cache ./gradlew buildDeb -x test && \
> dpkg -i ./front50-web/build/distributions/*.deb && \
> cd .. && \
> rm -rf workdir
> CMD ["/opt/front50/bin/front50"]{color}
> The image works fine with the docker containerizer, but the universal
> containerizer shows the following in stderr.
> "Failed to chdir into current working directory '/workdir': No such file or
> directory"
> The problem comes from the fact that the Dockerfile creates a workdir but
> then later removes the created dir as part of a RUN. The docker containerizer
> has no problem with it if you do
> docker run -ti --rm quay.io/spinnaker/front50:master bash
> you get into the working dir, but the universal containerizer fails with the
> error.
> thanks for your help,
> Michael
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (MESOS-7652) docker image not working with universal containerizer
[ https://issues.apache.org/jira/browse/MESOS-7652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] michael beisiegel updated MESOS-7652: - Description: hello, used the following docker image recently quay.io/spinnaker/front50:master https://quay.io/repository/spinnaker/front50 Here the link to the Dockerfile https://github.com/spinnaker/front50/blob/master/Dockerfile The image works fine with the docker containerizer, but the universal containerizer shows the following in stderr. "Failed to chdir into current working directory '/workdir': No such file or directory" The problem comes from the fact that the Dockerfile creates a workdir but then later removes the created dir as part of a RUN. The docker containerizer has no problem with it if you do docker run -ti --rm quay.io/spinnaker/front50:master bash you get into the working dir, but the universal containerizer fails with the error. thanks for your help, Michael was: hello, used the following docker image recently quay.io/spinnaker/front50:master https://quay.io/repository/spinnaker/front50 Here the link to the Dockerfile https://github.com/spinnaker/front50/blob/master/Dockerfile The image works fine with the docker containerizer, but the universal containerizer shows the following in stderr. "Failed to chdir into current working directory '/workdir': No such file or directory" The problem comes from the fact that the Dockerfile creates a WORKDIR but then later removes the created dir as part of a RUN. The docker containerizer has no problem with it if you do docker run -ti --rm quay.io/spinnaker/front50:master bash you get into the working dir, but the universal containerizer fails with the error. thanks for your help, Michael > docker image not working with universal containerizer > - > > Key: MESOS-7652 > URL: https://issues.apache.org/jira/browse/MESOS-7652 > Project: Mesos > Issue Type: Bug > Components: containerization >Affects Versions: 1.2.1 >Reporter: michael beisiegel >Priority: Minor > > hello, > used the following docker image recently > quay.io/spinnaker/front50:master > https://quay.io/repository/spinnaker/front50 > Here the link to the Dockerfile > https://github.com/spinnaker/front50/blob/master/Dockerfile > The image works fine with the docker containerizer, but the universal > containerizer shows the following in stderr. > "Failed to chdir into current working directory '/workdir': No such file or > directory" > The problem comes from the fact that the Dockerfile creates a workdir but > then later removes the created dir as part of a RUN. The docker containerizer > has no problem with it if you do > docker run -ti --rm quay.io/spinnaker/front50:master bash > you get into the working dir, but the universal containerizer fails with the > error. > thanks for your help, > Michael -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (MESOS-7652) docker image not working with universal containerizer
michael beisiegel created MESOS-7652: Summary: docker image not working with universal containerizer Key: MESOS-7652 URL: https://issues.apache.org/jira/browse/MESOS-7652 Project: Mesos Issue Type: Bug Components: containerization Affects Versions: 1.2.1 Reporter: michael beisiegel Priority: Minor hello, used the following docker image recently quay.io/spinnaker/front50:master https://quay.io/repository/spinnaker/front50 Here the link to the Dockerfile https://github.com/spinnaker/front50/blob/master/Dockerfile The image works fine with the docker containerizer, but the universal containerizer shows the following in stderr. "Failed to chdir into current working directory '/workdir': No such file or directory" The problem comes from the fact that the Dockerfile creates a WORKDIR but then later removes the created dir as part of a RUN. The docker containerizer has no problem with it if you do docker run -ti --rm quay.io/spinnaker/front50:master bash you get into the working dir, but the universal containerizer fails with the error. thanks for your help, Michael -- This message was sent by Atlassian JIRA (v6.3.15#6346)
