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
Cnest is hard coded to run sleep +Inf as the background process that is started for a nest container. It's just there to be started upon the first cnest command (podman exec) and to be killed when the last cnest (podman exec) session ends.
Is there some preferred init process that should be used instead of bash running sleep +Inf?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Cnest is hard coded to run
sleep +Inf
as the background process that is started for a nest container. It's just there to be started upon the first cnest command (podman exec) and to be killed when the last cnest (podman exec) session ends.Is there some preferred init process that should be used instead of bash running sleep +Inf?
Beta Was this translation helpful? Give feedback.
All reactions