Skip to content
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

Applications which use shared memory don't work, how can it be enabled? #29

Closed
bretton opened this issue Jan 5, 2025 · 4 comments
Closed
Labels
experience report Tell us about your experiences using Podman on FreeBSD question Further information is requested

Comments

@bretton
Copy link

bretton commented Jan 5, 2025

How do we enable shared memory inside freebsd podman containers?

I've tried setting the following in /usr/local/etc/containers/container.conf to various options with no effect:

ipcns = "shareable"

I've also tried setting the flag --shm-size 1g for buildah bud and podman run, where output of podman inspect cntid confirms:

"ShmSize": 1073741824,

however applications like postgresql won't work inside a freebsd podman container because:

FATAL:  could not create shared memory segment: Function not implemented
DETAIL:  Failed system call was shmget(key=2, size=56, 03600).

Where's the correct place to raise this question? Bugreport for podman/ocijail packages, or somewhere else for the base freebsd container itself?

@mnour mnour added experience report Tell us about your experiences using Podman on FreeBSD question Further information is requested labels Jan 6, 2025
@mnour
Copy link

mnour commented Jan 6, 2025

Hi @bretton,

Thanks for using and testing Podman on FreeBSD.

There are some details not finalised yet regarding initialising and configuring an OCI Container on FreeBSD whether with Podman or other container runtime engines, containerd for example. This is to be standardised at the level of FreeBSD container runtimes, namely ocijail and runj, which are the likes of runc but for FreeBSD Jails.

This is being actively discussed, specified and standardised as part of the wg-freebsd-runtime: 1) Proposal A - FreeBSD Jails, 2) Defining proposal A for FreeBSD jail configuration.

You are more than welcome and even encouraged to join the discussion or even join the bi-weekly calls. Details can be found:

@mnour
Copy link

mnour commented Jan 6, 2025

Hi @bretton!

Does this answer your question ?

@bretton
Copy link
Author

bretton commented Jan 7, 2025

Hi @mnour thanks, it looks like shared memory isn't implemented for the freebsd container, which severely limits the use cases at this stage. Meanwhile I'm up and running in 2mins with linux-based docker-compose setups.

Also there is no join option for the slack link at the "where can I get help" page. Only allows sign-ins from existing participants.

@bretton bretton closed this as completed Jan 7, 2025
@mnour
Copy link

mnour commented Jan 7, 2025

Hi @bretton!

Thanks a lot for your feedback and please whenever it is possible do try OCI Containers on FreeBSD and share any feedback, questions, requests or wishes. Any input is valuable 👊 .

For joining Slack, you are correct my bad. You can get an invite from OCI Slack, and then you can join the #wg-freebsd-runtime Slack Channel 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
experience report Tell us about your experiences using Podman on FreeBSD question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants