Thanks, Daniel. We’re configuring Podman on our shared-tenant HPC cluster with a job scheduler (Slurm), and we want to manage the local storage on compute nodes correctly. In particular, we want to make sure Podman usage doesn’t fill up node-local storage and interrupt other users. We already have these mechanisms to reclaim node-local storage: * At the end of each job, the job scheduler will flush TMPDIR * For persistent node-local storage (in /scratch), we have a daemon script that deletes the oldest files when /scratch starts to fill up. It’s good to know that podman uses TMPDIR, as our job scheduler will manage that. However, for rootless container storage, I feel like we will need to have subdirectories for each user (something like /scratch/containers/storage/$UID) and adapt our daemon to clear those out as needed. From: Daniel Walsh <dwalsh(a)redhat.com&gt; Date: Wednesday, October 11, 2023 at 2:47 PM To: podman(a)lists.podman.io <podman(a)lists.podman.io&gt; Subject: [Podman] Re: $TMPDIR in rootless_storage_path? On 10/11/23 15:22, Rahaman, Ronald O wrote: I’ve read that the rootless_storage_path setting interprets $HOME and $UID. Does it interpret $TMPDIR or any other variables? Podman uses $TMPDIR if set, but this has nothing to do with the rootless_storage_path. Thanks, Ron -------- Ron Rahaman Research Scientist II, Research Software Engineer Partnership for an Advanced Computing Environment (PACE) Georgia Institute of Technology _______________________________________________ Podman mailing list -- podman@lists.podman.io<mailto:podman@lists.podman.io> To unsubscribe send an email to podman-leave@lists.podman.io<mailto:podman-leave@lists.podman.io>