-
Notifications
You must be signed in to change notification settings - Fork 219
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
shm_open doesn't work #9
Comments
I can reproduce this with:
However, this works:
|
That tells me that
|
Rootless podman shuld mount a tmpfs at /dev/shm by default. Until that happens, it's worked around by explicitly specifying the mount point. Also, the --shm-size flag isn't working with rootless podman [1], so --tmpfs is used instead. It tries to mimic the in-kernel tmpfs default [2] of using half the amount of total RAM. If for some reason /proc/meminfo can't be parsed, it falls back to using podman's default of 65536k for tmpfs. It's not clear whether podman uses kibibytes or kilobytes for 'k'. The former was picked here for consistency. [1] containers/podman#1770 [2] https://www.kernel.org/doc/Documentation/filesystems/tmpfs.txt #9
Does PR #12 fix the problem for you? |
Rootless podman shuld mount a tmpfs at /dev/shm by default. Until that happens, it's worked around by explicitly specifying the mount point. Also, the --shm-size flag isn't working with rootless podman [1], so --tmpfs is used instead. It tries to mimic the in-kernel tmpfs default [2] of using half the amount of total RAM. If for some reason /proc/meminfo can't be parsed, it falls back to using podman's default of 65536k for tmpfs. It's not clear whether podman uses kibibytes or kilobytes for 'k'. The former was picked here for consistency. [1] containers/podman#1770 [2] https://www.kernel.org/doc/Documentation/filesystems/tmpfs.txt #9
Rootless podman shuld mount a tmpfs at /dev/shm by default. Until that happens, it's worked around by explicitly specifying the mount point. Also, the --shm-size flag isn't working with rootless podman [1], so --tmpfs is used instead. It tries to mimic the in-kernel tmpfs default [2] of using half the amount of total RAM. If for some reason /proc/meminfo can't be parsed, it falls back to using podman's default of 65536k for tmpfs. It's not clear whether podman uses kibibytes or kilobytes for 'k'. The former was picked here for consistency. [1] containers/podman#1770 [2] https://www.kernel.org/doc/Documentation/filesystems/tmpfs.txt #9
I am closing this issue because the above Either way, thanks for trying |
Hi,
when I run a playbook inside the fedora-toolbox created container it returns the following error:
ERROR! Unable to use multiprocessing, this is normally caused by lack of access to /dev/shm: [Errno 30] Read-only file system
The text was updated successfully, but these errors were encountered: