mirror of
https://github.com/podman-container-tools/podman.git
synced 2026-09-06 07:37:49 +00:00
0bd0ad5943
While resolving `workdir` we mostly create a `workdir` when `stat` fails with `ENOENT` or `ErrNotExist` however following cases are not true when user explicitly specifies a `workdir` while `running` using `--workdir` which tells `podman` to only use workdir if its exists on the container. Following configuration is implicity set with other `run` mechanism like `podman play kube` Problem with explicit `--workdir` or similar implicit config in `podman play kube` is that currently podman ignores the fact that workdir can also be a `symlink` and actual `link` could be valid. Hence following commit ensures that in such scenarios when a `workdir` is not found and we cannot create a `workdir` podman must perform a check to ensure that if `workdir` is a `symlink` and `link` is resolved successfully and resolved link is present on the container then we return as it is. Docker performs a similar behviour. Signed-off-by: Aditya R <arajan@redhat.com> |
||
|---|---|---|
| .. | ||
| basicalpine | ||
| envwithtab | ||
| squash | ||
| workdir-symlink | ||
| anothersecret.txt | ||
| context_dir_a_file | ||
| Dockerfile.test-cp-root-dir | ||
| Dockerfile.with-multiple-secret | ||
| Dockerfile.with-secret | ||
| Dockerfile.with-secret-verify-leak | ||
| secret.txt | ||