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

--ipc parameters differ from Docker, lack none option #13265

Closed
srcshelton opened this issue Feb 17, 2022 · 2 comments · Fixed by #13583
Closed

--ipc parameters differ from Docker, lack none option #13265

srcshelton opened this issue Feb 17, 2022 · 2 comments · Fixed by #13583
Assignees
Labels
Good First Issue This issue would be a good issue for a first time contributor to undertake. kind/feature Categorizes issue or PR as related to a new feature. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments.

Comments

@srcshelton
Copy link
Contributor

Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)

/kind feature

Description

Docker IPC options, documented at https://docs.docker.com/engine/reference/run/#ipc-settings---ipc, consist of "", "none", "private", "shareable", "container:<name|id>", "host".

podman-4.0.0-rc5 supports - accounting to podman-run(1) - "container:<id>", "host", and "ns:<path>".

This means that a docker-run command using almost any of the Docker --ipc options (other than "host" or "container:" with an ID) will fail with podman (including, the man-page suggests, referencing a container by name).

Of particular interest here is the "none" option to avoid having a large number of otherwise unused shm mountpoints on the host system.

Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide? (https://github.com/containers/podman/blob/main/troubleshooting.md)

Yes

@openshift-ci openshift-ci bot added the kind/feature Categorizes issue or PR as related to a new feature. label Feb 17, 2022
@mheon
Copy link
Member

mheon commented Feb 17, 2022

Seems easy enough to add

@mheon mheon added the Good First Issue This issue would be a good issue for a first time contributor to undertake. label Feb 17, 2022
@github-actions
Copy link

A friendly reminder that this issue had no activity for 30 days.

@rhatdan rhatdan self-assigned this Mar 21, 2022
rhatdan added a commit to rhatdan/podman that referenced this issue Apr 12, 2022
@github-actions github-actions bot added the locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. label Sep 20, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 20, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Good First Issue This issue would be a good issue for a first time contributor to undertake. kind/feature Categorizes issue or PR as related to a new feature. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants