-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
race: podman-remote run -it : stty: standard input #9859
Labels
flakes
Flakes from Continuous Integration
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.
remote
Problem is in podman-remote
Comments
edsantiago
added
flakes
Flakes from Continuous Integration
kind/bug
Categorizes issue or PR as related to a bug.
remote
Problem is in podman-remote
labels
Mar 29, 2021
You saw this post my PR getting merged? |
Yes, in fact you deliberately re-added the |
A friendly reminder that this issue had no activity for 30 days. |
still present in 4ca34fc |
A friendly reminder that this issue had no activity for 30 days. |
Luap99
added a commit
to Luap99/libpod
that referenced
this issue
Jun 4, 2021
There is race condition in the remote client attach logic. Because the resize api call was handled in an extra goroutine the container was started before the resize call happend. To fix this we have to call resize in the same goroutine as attach. When the first resize is done start a goroutine to listen on SIGWINCH in the background and resize again if the signal is received. Fixes containers#9859 Signed-off-by: Paul Holzinger <[email protected]>
mheon
pushed a commit
to mheon/libpod
that referenced
this issue
Jun 11, 2021
There is race condition in the remote client attach logic. Because the resize api call was handled in an extra goroutine the container was started before the resize call happend. To fix this we have to call resize in the same goroutine as attach. When the first resize is done start a goroutine to listen on SIGWINCH in the background and resize again if the signal is received. Fixes containers#9859 Signed-off-by: Paul Holzinger <[email protected]> <MH: Fixed cherry-pick conflicts> Signed-off-by: Matthew Heon <[email protected]>
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 21, 2023
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
flakes
Flakes from Continuous Integration
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.
remote
Problem is in podman-remote
Almost certainly related to #9831 / #9833
In window 1:
$ ./bin/podman system service --timeout=0
In window 2:
The "Container does not exist" warning is correlated with
--rm
.Once in a while, the
stty
will succeed:[UPDATED 2021-03-29 because I forgot to mention the workaround]
Workaround: add a
sleep
:The text was updated successfully, but these errors were encountered: