A non-trivial amount of people want to do things like running their code editor outside of the WebKit SDK but still have clangd work. In order to get this working, there must be a way to invoke a command in the container from the host and get its stdin, stdout and stderr just as clean as if it was invoked directly inside the container, not polluted by messages like this:
wkdev-enter: Launch a command or spawn an interactive shell in a container built by 'wkdev-create'
-> Mounting host Wayland socket (wayland-0).
-> Mounting host Pipewire socket (pipewire-0).
Using clangd like this is just an example. You can imagine many other use cases where you need to execute commands in the container from the host and have a program in the host process the output and/or communicate with it.
ntrrgc
commented
5 days ago
A non-trivial amount of people want to do things like running their code editor outside of the WebKit SDK but still have clangd work. In order to get this working, there must be a way to invoke a command in the container from the host and get its stdin, stdout and stderr just as clean as if it was invoked directly inside the container, not polluted by messages like this:
Using clangd like this is just an example. You can imagine many other use cases where you need to execute commands in the container from the host and have a program in the host process the output and/or communicate with it.