The reason why I am using unshare -r is because the command is ultimately run inside of an environment where further uid delegation is not possible. But that is a different story.
However, when creating the build container podman attempts to create it in /var/cache/containers which is not accessible to podman because of the root uid mapping. I also don't want podman to write anything there but everything has to happen inside a sandbox. As it can be seen from the command above root, runroot, and tmpdir are set. I would expect everything to be placed inside these directories but yet podman still attempts to access /var/cache.
Is there another option that can be set (and which I missed) or is that indeed a bug?
Issue Description
I am running podman-compose as follows which in turn calls podman:
The reason why I am using
unshare -r
is because the command is ultimately run inside of an environment where further uid delegation is not possible. But that is a different story.However, when creating the build container podman attempts to create it in
/var/cache/containers
which is not accessible to podman because of the root uid mapping. I also don't want podman to write anything there but everything has to happen inside a sandbox. As it can be seen from the command aboveroot
,runroot
, andtmpdir
are set. I would expect everything to be placed inside these directories but yet podman still attempts to access/var/cache
.Is there another option that can be set (and which I missed) or is that indeed a bug?
Steps to reproduce the issue
Just run:
Describe the results you received
The following error message:
Describe the results you expected
This is the output of a successful build:
podman info output
Podman in a container
No
Privileged Or Rootless
None
Upstream Latest Release
Yes
Additional environment details
Additional environment details
Additional information
Additional information like issue happens only occasionally or issue happens with a particular architecture or on a particular setting