You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I tried to start a very simple container through a Python script, and it happens that after runc exits, the shell input is "blocked" or "hidden":
With bash (version 5.0), you can type things, but it will not appear on the screen and you have to type "reset" + enter to reset the terminal and then be able to see what you are typing again
With sh, it just blocks the terminal in __GI___libc_read (fd=0, buf=0x55c6697d1ac0, nbytes=8192) call and you have to kill it
To setup the container, i just created a /tmp/roots directory, mount binded my / into it and used this configuration file generated from runc spec after having removed the mounts part:
Hello everyone and thank you for the great work 👍
I tried to start a very simple container through a Python script, and it happens that after runc exits, the shell input is "blocked" or "hidden":
__GI___libc_read (fd=0, buf=0x55c6697d1ac0, nbytes=8192)
call and you have to kill itTo setup the container, i just created a /tmp/roots directory, mount binded my / into it and used this configuration file generated from
runc spec
after having removed themounts
part:The Python script is very simple:
Looking at other issues, i found that it might be related to #1721 because if i set terminal to false, it works fine.
I am using runc 1.0-rc6 on kernel 4.20.0
The text was updated successfully, but these errors were encountered: