Count bind mount with overlay a folder that contains the overlay machinery (typically $HOME) #17932
Labels
kind/bug
Categorizes issue or PR as related to a bug.
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
Issue Description
Hi,
I am trying basically to run images on a RHEL 9 machine, keeping my own user (so using --userns=keep-id, which for huge images brings issues like #16541 but that's another story), but I don't wish these images to modify my
$HOME
(while still having my existing$HOME
files available). It seems the overlay machinery is unable to create an overlay when it the folder being bind mounted actually contains the internal podman storage files (so upper/lower/workdir/merged directories).In other words, in a rootless configuration, this doesn't work:
But overlay bind-mounting any subfolder of
$HOME
which isn't doesn't contain${HOME}/.local/share
is fine. For example this works fine:I was wondering if this is expected ? In the end I would like to run something like:
and act "as if" my user inside the container was kind of the same than the user outside the container, but with no change of
${HOME}
propagated back to my real${HOME)
.PS: I have heard about toolbox (https://docs.fedoraproject.org/en-US/fedora-silverblue/toolbox/) but I didn't try yet and I don't know if it does more or less what I am trying to do directly with podman.
Cheers,
Romain
Steps to reproduce the issue
Steps to reproduce the issue
$HOME
):Describe the results you received
Describe the results you expected
It should work without error.
podman info output
I tried the above in the `quay.io/podman/upstream` image started in `--privileged` mode. I also tried this on my RHEL 9 VM, which currently has podman 4.2.
Podman in a container
No
Privileged Or Rootless
Rootless
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
The text was updated successfully, but these errors were encountered: