Asking each user that wants to employ rootless podman to do these or similar steps is less desirable than having admin do a system-wide config once.

On Thu, Oct 10, 2019 at 5:09 PM Daniel Walsh <dwalsh@redhat.com> wrote:
On 10/8/19 9:29 AM, Matt Heon wrote:
On 2019-10-08 08:13, Lou DeGenaro wrote:
I start with an empty /home/degenaro/.config/containers directory.
I run podman info.
I see that files libpod.conf and storage.conf have been created.
I grep for "/home" and see:
libpod.conf:volume_path =
"/home/degenaro/.local/share/containers/storage/volumes"
libpod.conf:static_dir =
"/home/degenaro/.local/share/containers/storage/libpod"
storage.conf:  graphroot = "/home/degenaro/.local/share/containers/storage"

What's wanted is to configure podman so that "/home" is replaced by
"/tmp".  That is, if I were to erase these .conf files and run podman info
again I want to see:

ibpod.conf:volume_path =
"/tmp/degenaro/.local/share/containers/storage/volumes"
libpod.conf:static_dir =
"/tmp/degenaro/.local/share/containers/storage/libpod"
storage.conf:  graphroot = "/tmp/degenaro/.local/share/containers/storage"

The desire is to have all rootless users use /tmp instead of /home, since
/home is on a shared filesystem which seems to be problematic for podman.

Thx.

Lou.

_______________________________________________
Podman mailing list -- podman@lists.podman.io
To unsubscribe send an email to podman-leave@lists.podman.io

There is presently no way to set the directories rootless Podman will
use automatically ahead of running 'podman' for the first time for a
user (save procedurally generating a config file for them before it
runs). However, if you can log into each user once and run a simple
Podman command with a few flags, you can set up the config files to
point where you want them to.

With the '--root', '--runroot', and '--tmpdir' global flags, you can
tell Podman where to put its storage. You will need to point all of
these to separate directories (they can all be subdirectories of the
place in /tmp where the user's Podman files are stored, but they need
to be different subdirectories). If Podman has never run before and no
config file has been generated, it will be generated using the
directories given with those three flags. I've previously advised
someone in a similar situation to 'su' to each user running Podman and
run a simple 'podman info' command with those flags to preload a sane
configuration.

If you'd like a way to do this automatically (specify a base directory
outside of /home where rootless Podman will place its configuration),
I'd recommend you file a feature request.

Thanks,
Matt Heon

_______________________________________________
Podman mailing list -- podman@lists.podman.io
To unsubscribe send an email to podman-leave@lists.podman.io

How about you just bind mount a directory from /tmp onto /home/USER/.local/share/containers

That should solve the issue.

# mkdir /tmp/dwalsh

# chown dwalsh:dwalsh /tmp/dwalsh

# mkdir ~dwalsh/.local/share/containers

# mount --bind /tmp/dwalsh ~dwalsh/.local/share/containers

# su - dwalsh

$ podman run fedora echo hello

Most likely you

_______________________________________________
Podman mailing list -- podman@lists.podman.io
To unsubscribe send an email to podman-leave@lists.podman.io