-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Rootless API not usable right after image is deleted #9251
Comments
This call should be very quick. It is the first all that cockpit-podman does. Unfortunately often the first call gets stuck, see: containers/podman#8762 containers/podman#9251 When the call is stuck, the whole page is stuck in `Loading...`. When we just reject it, the `Loading...` state moves on and we are presented with alert to 'Start' the service. Clicking the button does the trick. It is kind of hacky, but I think it is more user friendly then just being stuck on a page.
The first rootless call often gets stuck or fails. In such case we have alert banner to start the service (or just empty state). A real user would just hit the button so lets do the same as this is always getting back to us and we waste too much time reporting to podman with mixed results. Examples: containers/podman#8762 containers/podman#9251 containers/podman#6660
This call should be very quick. It is the first all that cockpit-podman does. Unfortunately often the first call gets stuck, see: containers/podman#8762 containers/podman#9251 When the call is stuck, the whole page is stuck in `Loading...`. When we just reject it, the `Loading...` state moves on and we are presented with alert to 'Start' the service. Clicking the button does the trick. It is kind of hacky, but I think it is more user friendly then just being stuck on a page.
The first rootless call often gets stuck or fails. In such case we have alert banner to start the service (or just empty state). A real user would just hit the button so lets do the same as this is always getting back to us and we waste too much time reporting to podman with mixed results. Examples: containers/podman#8762 containers/podman#9251 containers/podman#6660
I think my results are correct?
|
seems so. Have you started with rootless service not running? |
A friendly reminder that this issue had no activity for 30 days. |
This looks like rootless podman socket is not hanlding socket activation correctly. |
@jwhonce Any idea what is going on here? |
Simpler repeater
Hangs
Succeds, the question is whether this is podman issue or systemd. One would figure it is podman. |
More information, if I kill the podman pause container off it works fine.
Now I wait for the podman service to exit
|
If I kill the curl and try again it works. It is something about the pause container/joining the user namespace that is getting the confused. |
PR opened here: #9855 |
if LISTEN_FDS is specified by systemd, we need to use the first fd after the std files (so fd=3) to read from the activation socket instead of manually opening the UNIX socket. [NO TESTS NEEDED] Closes: containers#9251 Signed-off-by: Giuseppe Scrivano <[email protected]>
if LISTEN_FDS is specified by systemd, we need to use the first fd after the std files (so fd=3) to read from the activation socket instead of manually opening the UNIX socket. [NO TESTS NEEDED] Closes: containers#9251 Signed-off-by: Giuseppe Scrivano <[email protected]>
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
In Cockpit tests we saw one test failing way too many times so I played with it. It is timing issue, possibly some race as sleeping just one second resolves this.
Steps to reproduce the issue:
Prerequisites:
podman rmi fedora:33
in the following script needs to physically remove it, if it just untags it, then it works just fine).chmod u+x
it and run it as normal user.Describe the results you received:
The first API access just hangs and is killed by timeout.
The second API access fails.
The third API access succeeds.
Describe the results you expected:
All API calls succeed.
Output of
podman version
:Package info (e.g. output of
rpm -q podman
orapt list podman
):But this is not current regression in podman-3, we see this on current F33 as well.
Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide?
Yes
The text was updated successfully, but these errors were encountered: