Podman does not use tmpdir specified in --tmpdir

[cwrx777]

Podman version:

version:
  APIVersion: 4.9.4-rhel
  GoVersion: go1.21.13 (Red Hat 1.21.13-3.module+el8.10.0+22345+acdd8d0e)
  Version: 4.9.4-rhel

I run rootless podman and specify --tmpdir in the command as follows:

podman play kube $YAML_DIR/$TEMP_KUBE_YAML  \
    --replace  \
    --service-container=true \
    --configmap=$YAML_DIR/$CONFIGMAP_YAML \
    --network ${NETWORK_NAME}\
    --events-backend=file \
    --tmpdir=${MY_TMPDIR} \
    --log-level=debug

The rootless user has rwx access to the ${MY_TMPDIR}.
However, the actual tmpdir used is /run/user/1024/libpod/tmp where 1024 is the id of the rootless podman user.
I can see there events.log were created in tmpdir\events.

drwx-----T.  3 rootless_user rootless_user  60 Nov 18 15:15 ..
-rw-r--r--.  1 rootless_user rootless_user   0 Nov 18 15:15 alive.lck
-rw-------.  1 rootless_user rootless_user   4 Nov 18 15:15 pause.pid
-rw-r--r--.  1 rootless_user rootless_user   0 Nov 18 15:15 alive
srwxr-xr-x.  1 rootless_user rootless_user   0 Nov 18 15:15 5b320bfd6d4646ed01130917f43a6e3eefc87c98f8998e6be5067d77fcfcf765.net
-rw-r--r--.  1 rootless_user rootless_user   0 Nov 18 15:46 rootless-netns.lock
drwx------.  4 rootless_user rootless_user 120 Nov 18 15:46 rootless-netns
drwx------.  2 rootless_user rootless_user  80 Nov 18 15:46 rootlessport486094596
drwx------.  2 rootless_user rootless_user  80 Nov 18 15:48 rootlessport3686046440
drwx------.  2 rootless_user rootless_user  80 Nov 18 15:55 rootlessport2429694777
drwx------.  2 rootless_user rootless_user  80 Nov 19 13:59 rootlessport3963862616
drwx------.  2 rootless_user rootless_user  80 Nov 19 15:43 rootlessport3324992620
drwx------.  2 rootless_user rootless_user  80 Nov 21 11:12 rootlessport2960463238
srwxr-xr-x.  1 rootless_user rootless_user   0 Nov 28 23:41 bb748db557e886932c5fced5dcd362c3828647b7cbb9e19386c479a74519315c.net
drwx------.  2 rootless_user rootless_user  80 Nov 29 11:50 events
drwxr-x---.  2 rootless_user rootless_user  40 Nov 29 12:23 exits
drwxr-x--x. 13 rootless_user rootless_user 380 Nov 29 12:23 .
drwx------.  2 rootless_user rootless_user  80 Nov 29 12:23 rootlessport1487873305
drwx------.  2 rootless_user rootless_user 180 Nov 29 12:23 rp

[eriksjolund]

I searched for the --tmpdir option:

$ podman kube play --help | grep tmpdir
$ 

$ podman --help | grep tmpdir
      --tmpdir string               Path to the tmp directory for libpod state content.
$

There is no option --tmpdir here:
https://docs.podman.io/en/latest/markdown/podman-kube-play.1.html

but there is one here:
https://docs.podman.io/en/latest/markdown/podman.1.html#tmpdir-path

The order of the options is probably important.
I guess it should be

podman --tmpdir=${MY_TMPDIR} kube play ...

[Luap99]

Storage paths are set on first libpod db creation and will be overwritten from the db each time, just look at the --log-level debug output, i.e.

DEBU[0000] Overriding tmp dir "/tmp" with "/run/user/1000/libpod/tmp" from database

If you want to change these paths you should set all of --root/--runtroot/--tmpdir to create a fully separated storage, chaining only one of them is not good at would likely cause all sorts of weird issues/conflicts.