Podman volume mapping again

[Mark_Ryan]

Hi,

I'm a network engineer more than I am Linux engineer, I'm also switching from Docker to Podman for corporate reasons. So I'm on a learning curve.

I'm trying to get an alpine linux based container with python up and running on RHEL 8. All works fine until I try and map a volume. If I just use a normal podman volume without the options or don't bother with a map the container runs. It did all work on WSL which is Ubuntu so all good in theory.

I referred to this post:

Solved: Podman volume mounts, rootless container, and non-... - Red Hat Learning Community

I've also tried using the --users option using the root ID which the container side was built under but I still get.

Error: lsetxattr /myfolder operation not permitted

podman volume create --opt type=none --opt device=/myfolder --opt o=bind myvolume
podman run --network=host --name mypython-01 -d -it -v "myvolume:/app/workdir:Z" mypython:1.0

Something to do with SE Linux context of myfolder has been hinted at by a colleague?

Thanks in advance for any advice.

[Mark_Ryan]

Dropped the Z and that allowed the container to spin up but access to the volume wasn't allowed so for the time being I've disabled security. So I'm up and running but it isn't ideal.

So back down to users again willd rop the Z nad try the user IDs