subsystemctl
subsystemctl copied to clipboard
sorah
Utility to run systemd in WSL2 with a Linux namespace
Just a quick note to let you know that I've had a patch accepted into AppArmor (and have a similar one awaiting review for snapd) to support running under WSL:...
Adds two new options to the shell command: `--exclude-env` will copy all environment variables except the ones specified in the list. `--include-env` will only copy the variables specified in the...
Executing `echo $WSL_DISTRO_NAME` in `subsystemctl shell` currently doesn't work, others environment variables such as `$DISPLAY` isn't inherited too. I think it is good to have a way to specify a...
So `subsystemctl` is designed to work with root privilege, which I fully acknowledge, but recently I've been experimenting with `chmod +s` on the executable. What I noticed is that, after...
The `glxlgears` works just fine, but executing it inside the subsystemctl says that it `couldn't open display :0` In this case i use WSL Graphic via /dev/dxg ``` [root@LAPTOP ~]#...
○ → /root/.cargo/bin/subsystemctl exec bash error: Found argument 'bash' which wasn't expected, or isn't valid in this context USAGE: subsystemctl exec [FLAGS] [OPTIONS] [-- ...] For more information try --help...
Running `subsystemctl exec -- echo 1` will normally prints `1`, but if you run it in a ssh session, it will show this: ``` thread 'main' panicked at 'called `Result::unwrap()`...
fixes #11
While in the environment `cat /proc/sys/fs/binfmt_misc/WSLInterop` produces this error ``` Too many levels of symbolic links ``` This breaks [wslu](https://github.com/wslutilities/wslu)
I was able to run the subsystemctl in Centos 8, however, it is the same with genie, there are few application that are depreciated, like the firewalld. All you need...