Skip to content
This repository has been archived by the owner on Jan 25, 2022. It is now read-only.

Docker creates the WORKDIR if it doesn't already exist. Garden does not. #29

Closed
onsi opened this issue Mar 31, 2015 · 2 comments
Closed

Comments

@onsi
Copy link
Contributor

onsi commented Mar 31, 2015

This is coming out an issue surfaced in Lattice:
https://github.com/cloudfoundry-incubator/lattice/issues/66

When spinning up a Docker container Docker always creates the requested working directory (whether it is part of the Dockerfile WORKDIR or specified via docker run -w /foo). Garden-Linux does not reproduce this behavior and, as a result, Docker images that specify nonexisting WORKDIRs fail with chdir: No such file or directory.

The most straightforward path forward is probably to emulate Docker's behavior (and document it). Thoughts?

@cf-gitbot
Copy link

We have created an issue in Pivotal Tracker to manage this. You can view the current status of your issue at: https://www.pivotaltracker.com/story/show/91550852.

@goonzoid
Copy link
Contributor

Closing here since we have an issue in tracker with ongoing discussion.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants