You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 25, 2022. It is now read-only.
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?
The text was updated successfully, but these errors were encountered:
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 withchdir: No such file or directory
.The most straightforward path forward is probably to emulate Docker's behavior (and document it). Thoughts?
The text was updated successfully, but these errors were encountered: