-
Notifications
You must be signed in to change notification settings - Fork 220
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
Forked app not considered when running toolbox run #1038
Comments
Distrobox has exactly the same behaviour with |
According to flatpak webex issue, Webex even uses combination of |
doesn't seem like there's much to do on this issue - The behaviour described seems to be working as expected - podman grabs a handle of the parent process not the child. You should be able to just wrap it in a script: |
As @akdev1l mentioned ... I am not sure if Toolbx can really do anything here. If you are working on a launcher for an application like that (uses It's difficult for Toolbx to know what the intended behaviour is, because it depends on the process. eg., the current behaviour you are seeing could be considered OK for a daemon. |
Closing! Thanks for your interest in Toolbx, and trying to make Webex work (especially with Flatpak)! |
Is your feature request related to a problem? Please describe.
Basically, when i try to run forking app, after it forks - toolbox considers that container needs to be removed and does that, even if forked app was still working on the background.
Describe the solution you'd like
Forking app should be considered when running programs using
toolbox run
and it should not destroy container before forked app closesAdditional context
Initially, i wanted to run Webex app in toolbox (f33, because of libsecret library compatibilities), so far it worked good when i used
toolbox enter
, but when i started integrating it with desktop usingtoolbox run
, i quickly realised that it is being destroyed right after it starts.This C code sample should provide reliable example of toolbox killing container before forking app closes.
Steps:
testfork.c
:Compile using gcc:
gcc testfork.c
Run using toolbox:
toolbox run ./a.out
Expect output like so (with last line appearing after 2 seconds of delay):
But it will show (flawed) output like this:
Debug log of that launch
The text was updated successfully, but these errors were encountered: