[MESOS-7652] Docker image with universal containerizer does not work if WORKDIR is missing in the rootfs.

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 1.2.1
• Fix Version/s: 1.2.3, 1.3.2, 1.4.0
• Component/s: containerization
• Labels: mesosphere
• Target Version/s: 1.2.3, 1.3.2, 1.4.0
• Epic Link: Unified Container
• Sprint: Mesosphere Sprint 60, Mesosphere Sprint 61
• Story Points: 3
• Assignee: Gilbert Song
• Reporter: michael beisiegel
• Shepherd: Jie Yu
• Created: 10/Jun/17 02:39
• Updated: 17/Aug/17 08:28
• Resolved: 17/Aug/17 08:28

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
FROM java:8

MAINTAINER [e-mail]

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"]

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