summaryrefslogtreecommitdiff
path: root/transfer.md
diff options
context:
space:
mode:
authorAditya R <arajan@redhat.com>2022-03-02 15:07:06 +0530
committerAditya R <arajan@redhat.com>2022-03-02 19:02:33 +0530
commit0bd0ad59436436e93ac81ce46059d8618ed7766c (patch)
treeed3c97ca2cb90b11b557b4db9dcab97ee2e623c6 /transfer.md
parent7877b02aacf3e8d3d37f6283c6b8aa81688fd120 (diff)
downloadpodman-0bd0ad59436436e93ac81ce46059d8618ed7766c.tar.gz
podman-0bd0ad59436436e93ac81ce46059d8618ed7766c.tar.bz2
podman-0bd0ad59436436e93ac81ce46059d8618ed7766c.zip
container: workdir resolution must consider symlink if explicitly configured
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>
Diffstat (limited to 'transfer.md')
0 files changed, 0 insertions, 0 deletions