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
docker exec hang #6154
Comments
We cannot return the container ID 'cause that can make moby think that the container process itself exits. Let's return a fake pid 0 here. Fixes: kata-containers#6154 Signed-off-by: Peng Tao <bergwolf@hyper.sh>
We cannot return the container ID 'cause that can make moby think that the container process itself exits. Let's return a fake pid 0 here. Fixes: kata-containers#6154 Signed-off-by: Peng Tao <bergwolf@hyper.sh>
Should this be closed? @bergwolf |
Not until we merge the PR in Moby, in my opinion. It looks like GitHub has even set it up to auto-close. |
Looks like the auto-close doesn't work across orgs, despite the Web UI claiming so. Anyway, we've merged the fix for the Moby master branch, and the fix for 23.0 is in review for the next patch. I'd suggest this can be closed and those interested in the fixes can monitor the related PRs. |
Thanks @neersighted ! Let's close this as moby/moby#44892 has been merged. |
Reported by Jim Carroll from Mirantis:
terminal 1:
docker run --rm -it --name katatest --runtime io.containerd.kata.v2 alpine
terminal 2:
docker exec -it katatest /bin/sh
everything seems fine.
Until I try to exit the exec session, at which point the following happens:
I have to kill the exec command still hung in terminal 2 to regain control of that lost soul
The text was updated successfully, but these errors were encountered: