-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
allow file-descriptor passing from podman-exec #2372
Comments
So you want to add a --preserve-fds flag to podman run/create? |
Yes, but to podman run/exec, if I understood @chergert properly. |
It is an useful idea. The only issue is that we are already passing down a bunch of fds, so we would need to properly reassign them. |
The Flatpak way of doing this is |
@giuseppe Do you have time to work on it? |
There are probably going to be SELinux issues with this. SELinux should block the use of these fd's being passed in. |
Unless they are labeled with something like |
@giuseppe Could you take a look at this? |
PR for runc here: opencontainers/runc#1995 PR for libpod here: #2426 |
Allow to pass additional FDs to the process being executed. Closes: containers#2372 Signed-off-by: Giuseppe Scrivano <[email protected]>
/kind feature
Description
Add support for passing file-descriptors across
podman exec
execution boundary.I've started integrating some basic podman support into GNOME Builder using our native container abstractions (like we do for flatpak). One thing that makes this possible with flatpak is that we can pass file descriptors across the execution boundary. That way, I can feed a PTY for the debugger inferior to tooling like gdb while using the controlling PTY to control gdb itself.
I've looked at calling runc directly using --preserve-fds, but that would mean duplicating a lot of what podman already does for us.
The text was updated successfully, but these errors were encountered: