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
SIGSEGV when using 'podman run --pod="new:<pod-name>" <containerimage>' #2124
Comments
|
$ podman run --pod="new:test" -d fedora sleep 1000 This works for me. Not sure what you are trying to do. Of course the tool should not segfault. |
|
|
The segfault is somewhere in c/image and happens when creating the infra container Can you trigger this with |
|
@Logibox Is this running as rootless? |
|
@rhatdan the pause-amd64 container was just used as an example, but seems to occur with all other images too. I missed the pull command (which has the tag) i ran before the run in the original report. @mheon yes this is while running rootless.
|
|
Running rootless |
|
I can reproduce this with rootless, but not as root. |
|
@giuseppe PTAL |
Closes: containers#2124 Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
Closes: containers#2124 Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
Closes: containers#2124 Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
When using the 'new:..' syntax in --pod, to create a new pod on run, podman panics.
Steps to reproduce the issue:
podman pull gcr.io/google_containers/pause-amd64:3.0podman run --pod="new:test" gcr.io/google_containers/pause-amd64Describe the results you received:
Describe the results you expected:
To run the container in the newly created pod.
Additional information you deem important (e.g. issue happens only occasionally):
Output of
podman version:Output of
podman info:Additional environment details (AWS, VirtualBox, physical, etc.):
This occurs when running rootless.
The text was updated successfully, but these errors were encountered: