run --workdir=/nonesuch: chdir: No such file or directory: OCI runtime command not found error

[edsantiago]

# podman run --workdir=/nonesuch alpine pwd
Error: chdir: No such file or directory: OCI runtime command not found error
# echo $?
127
(expected: "/nonesuch" and exit 0)

This is a change in longstanding behavior. I don't know what the correct behavior should be for this case, but it is a difference from docker and from all versions of podman up to now.

podman-1.8.0-0.1.fc31.x86_64
conmon-2.0.10-2.fc31.x86_64

Curiously, I cannot reproduce with podman @ master on f30.

[mheon]

Could this be runc vs crun?

[mheon]

Also, expected behavior is that the workdir will be created?

[edsantiago]

Oh, good call: it could very well be crun. Yes, expected behavior is to create the directory:

f30# podman run -it --workdir=/none/such alpine sh
/none/such # touch abc
/none/such # ls -l /none/such/abc
-rw-r--r--    1 root     root             0 Feb  4 17:56 /none/such/abc
/none/such #

[mheon]

@giuseppe PTAL

[rhatdan]

Yuck, I don't like the default. Basically this ends up with typos creating directories in the container...

[giuseppe]

yes this is a crun vs runc difference.

I can easily change it in crun if we agree on what behaviour makes more sense.

I agree with Dan and I think that chdir'ing to a not existing one should raise an error rather than creating it automatically

[rhatdan]

I am closing this since, I see this as a Bug in runc/docker, not something we should fix.