Yes it is 256:
island:backend [master]> cat /proc/sys/fs/mqueue/msg_max
256
On 20.05.2021 21:00, Daniel Walsh wrote:
On 5/20/21 08:29, Michael Ivanov wrote:
Hallo!
I'm trying to run my application in podman rootless container and I stumble
on following problem: my program needs /proc/sys/fs/mqueue/msg_max to be at
least 256, but in running container this value is just 10. When I try to
specify this parameter while running the image (--sysctl 'fs.mqueue.msg_max=256')
I get the following error:
Error: open /proc/sys/fs/mqueue/msg_max: Permission denied: OCI permission denied
and container is not created.
My host where container is being run has this parameter set to 256. How can I
expose current host setting for msg_max to my container?
Best regards,
When you login to your user account is is et to 256?
$ cat /proc/sys/fs/mqueue/msg_max
10
Ok I just recreated it, I think the issue is that we create a new procfs within the container, But it looks like this should be namespaced.
Works in rootfull mode, but not in rootless.
# podman run --sysctl 'fs.mqueue.msg_max=256' fedora cat
/proc/sys/fs/mqueue/msg_max
256
#
exit
podman (kube) $ podman run --sysctl 'fs.mqueue.msg_max=256' fedora
cat /proc/sys/fs/mqueue/msg_max
256
Error: open /proc/sys/fs/mqueue/msg_max: Permission denied: OCI
permission denied
bash: 256: command not found...
If this is blocked by the kernel, it might be a kernel bug. Since theoretically this is a namespaced object and should be modifiable within the container at least up to the size the user is able to use.
Giuseppe what do you think?
_______________________________________________
Podman mailing list -- podman@lists.podman.io
To unsubscribe send an email to podman-leave@lists.podman.io
-- \ / | | (OvO) | Михаил Иванов | (^^^) | | \^/ | E-mail: ivans@isle.spb.ru | ^ ^ | |
_______________________________________________ Podman mailing list -- podman@lists.podman.io To unsubscribe send an email to podman-leave@lists.podman.io