created pods are not startable #6818
Labels
kind/bug
Categorizes issue or PR as related to a bug.
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
stale-issue
Comments
openshift-ci-robot
added
the
kind/bug
|
Any more details here? I can't reproduce, the pod starts without issue. |
|
Perhaps its worth noting that I have cgroupsv2 enabled and use |
|
I tried to setup an reproducing environment but failed in the end (fresh OS install, same tools, same versions, everything). Is there anything suspicious in my |
|
Please provide: And any log messages from conmon that might be in your journal or syslog |
|
I just ran into this message myself running 2.0.1 rootless on Debian. Version infoCreating an empty pod: Trying to start it in debug mode: There's a couple different interesting bits in the debug log, but without debug podman just prints Possibly also interesting is the message when I try starting the infra container directly: It's hard to tell if my issue has the same root cause as OP's but maybe trying to start the infra container has a better error reporting route. |
|
It looks like we do return the errors in question - they must be dropped somewhere. Also, that error message is truly spectacularly bad - "container already exists" means absolutely nothing here. I think I was the one that wrote that bit, so... oops? |
|
Fix for the error reporting part of this in #6846 |
|
Also, any chance you can try using the |
|
Now that we know the ambiguous error message just means containers couldn't start, it's a bit easier to check stuff! Here's what I have on my setup: (I switched to btrfs since last post as my / is btrfs) I'm using the "Linux Apps - beta" feature on a Chromebook, so the env is pretty nonstandard. Not sure if this is the same issue trusch had, or if there's hope to get podman working here at all... (Docker works fine) |
|
@giuseppe Does the keyring issue look like a kernel issue to you? I think I recall that. |
|
A friendly reminder that this issue had no activity for 30 days. |
|
@giuseppe Did you ever review this? |
|
sorry I've missed it. Looks like the kernel is too old and have no support for keyrings. Both runc and crun have an option |
|
@giuseppe Do we need a way to pass this down through podman to the OCI runtimes? |
|
Hello, I just performed a full reformat of my Chromebook for unrelated reasons, & installed podman from the kubic debian repo. Rootful podman works great now which is excellent :) and unblocks me building stuff with podman. Rootless, I had to set up subuid/subgid files, then had a new error message about In any case, the messaging that started this whole ticket appears to be fixed: That's a real error message now! so it seems reasonable to me to close this ticket. |
github-actions
bot
added
the
locked - please file new issue/PR
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
If I create a pod, I expect that I can start it. Unfotunately this fails because the create step also already creates the infra container,
but the start step tries to create it. This is very annoying because the systemd files generated using
podman generate systemd --new ...rely on this behavior.Steps to reproduce the issue:
Describe the results you received:
I can't start the created pod
Describe the results you expected:
I can start the created pod
Additional information you deem important (e.g. issue happens only occasionally):
Output of
podman version:Output of
podman info --debug:Package info (e.g. output of
rpm -q podmanorapt list podman):Additional environment details (AWS, VirtualBox, physical, etc.):
Local laptop.
The text was updated successfully, but these errors were encountered: