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 want to be able to treat toolbox like a screen process, where I can detach and reattach to run long running tasks without needing the SSH session to be there all the time
Pressing ctrl-p followed by ctrl-q will normally allow detaching from interactive container processes, but does not work with the current toolbox, causing the following error:
toolbox:/ # ERRO[0015] detached from container
ERRO[0015] timed out waiting for file /var/lib/containers/storage/btrfs-containers/3d0fefc70c9edb1c284f50eaf377e9ef89fa6d3bbde6644e3d2225190a1ba509/userdata/d006575b972e4bd908349aa867c6e1848a6f87a4060e6a57854aba3370c6013b/exit/3d0fefc70c9edb1c284f50eaf377e9ef89fa6d3bbde6644e3d2225190a1ba509: internal libpod error
Error: non zero exit code: -1: OCI runtime error
This should be resolvable by using podman attach instead of exec to get into the container, at least I can emulate my desired behaviour with podman start toolbox-root, followed by podman attach toolbox-root for a container previously created by toolbox
There's something in the way toolbox cleans up after itself though that kills the container when I detach if I patch toolbox to use attach instead of exec
The text was updated successfully, but these errors were encountered:
I want to be able to treat toolbox like a screen process, where I can detach and reattach to run long running tasks without needing the SSH session to be there all the time
Pressing
ctrl-p
followed byctrl-q
will normally allow detaching from interactive container processes, but does not work with the current toolbox, causing the following error:toolbox:/ # ERRO[0015] detached from container
ERRO[0015] timed out waiting for file /var/lib/containers/storage/btrfs-containers/3d0fefc70c9edb1c284f50eaf377e9ef89fa6d3bbde6644e3d2225190a1ba509/userdata/d006575b972e4bd908349aa867c6e1848a6f87a4060e6a57854aba3370c6013b/exit/3d0fefc70c9edb1c284f50eaf377e9ef89fa6d3bbde6644e3d2225190a1ba509: internal libpod error
Error: non zero exit code: -1: OCI runtime error
This should be resolvable by using
podman attach
instead ofexec
to get into the container, at least I can emulate my desired behaviour withpodman start toolbox-root
, followed bypodman attach toolbox-root
for a container previously created by toolboxThere's something in the way toolbox cleans up after itself though that kills the container when I detach if I patch toolbox to use
attach
instead ofexec
The text was updated successfully, but these errors were encountered: