Separate image and container runtime locations for HPC environment #24141
Replies: 2 comments
-
NFS Servers will not allow a rootless user to chown files within a User Namespace. From the NFS servers point of view it looks like UID=1000 is attempting to chown a file to something other then 1000 and does permission denied.
|
Beta Was this translation helpful? Give feedback.
-
Thanks for confirming it should be possible. I'm seeing this error - is there any way I can override?
Looks like buildah copier related code |
Beta Was this translation helpful? Give feedback.
-
I'd like to be able to separate where Podman saves container images and where Podman runs containers. Context: this is an HPC environment with a number of Lustre and NFSv3 mounts and a single NFSv4 mount that is on a slow machine with slow disks. Podman is running in rootless mode.
My goal is to store the container images on the NFSv4 mount (no other options besides a ramdrive) and run the containers on a much faster NFSv3/Lustre mount.
Is this possible? I've tried modifying runroot/graphroot/rootless_storage_path with no luck.
Beta Was this translation helpful? Give feedback.
All reactions