What does that even mean?
Well, this gives you a way to run systemd as pid 1, with all the trimmings, inside WSL 2. It does this by creating a pid namespace, the eponymous poor-man's-container "bottle", starting up systemd in there, and entering it, and providing some helpful shortcuts to do so.
As explained here, if you are running Windows 11 and a version of WSL 0.67.6 or above. If this is available to you, you should use it instead of genie, because it's a much more elegant way of getting systemd to run.
It's not quite perfect, however, so you should also check out bottle-imp, my friendly helper to make working with WSL's native systemd support a little easier.
Using genie on systems that have native systemd support is not supported.
NOTE: Before you install genie for the first time, read ALL of this page. This will save you a great deal of trouble later on. Especially, please note that on many distributions you will encounter the problem described under "Warning: Timing Out" below when you first run genie, and will need to resolve it before your system will operate correctly.
It is a good idea to set your systemd default target to multi-user.target before installing genie. This is the target that genie is designed to work with, since the default graphical.target used by many distributions includes services for the graphical desktop that would take, at minimum, considerable reconfiguration before operating properly under the WSL/WSLg environment.
If you are using a custom kernel for WSL, it should comply with the suggested means of detecting WSL given in microsoft/WSL#423 (comment) - i.e., the string "microsoft" should be present in the kernel version string, which can be found in /proc/sys/kernel/osrelease. You can check this by running systemd-detect-virt; it should return "wsl".
Also read the WSLg FAQ and the known-problematic systemd units list for known problems and known solutions to them.
More information, tips & tricks, etc. are available on the genie wiki. Please consult it before opening an issue.
Note: it is only possible to run systemd (and thus genie ) under WSL 2; WSL 1 does not support the system calls required to do so. If you are running inside a distro configured as WSL 1, even if your system supports WSL 2, genie will fail to operate properly.
If there is a package available for your distribution, this is the recommended method of installing genie.
Dependent packages on Debian are daemonize, dbus, gawk, libc6 (>= 2.2.5), policykit-1, python3 (>= 3.7), python3-pip, python3-psutil, systemd (>= 232-25), and systemd-container (>= 232-25). These should all be in the distro and able to be installed automatically.
To install, add the wsl-translinux repository here by following the instructions here:
https://arkane-systems.github.io/wsl-transdebian/
then install genie using the commands:
sudo apt update
sudo apt install -y systemd-genieUse the above Debian package. For current Ubuntu releases and the timing-out problem, see the problematic units listed on the genie wiki.
An Arch package (.zst) can be downloaded from the releases, to right. Install it manually, using pacman -U <file>.
A Fedora package (.rpm) can be downloaded from the releases, to right. Install it manually, using dnf install <file>.
If your distribution supports any of the package formats available, you may wish to try downloading the relevant format and giving it a try. This will almost certainly need some tweaking to work properly.
Debian is the "native" distribution for genie , for which read, "what the author uses". Specifically, Debian buster+, with usrmerge installed. If you're using anything else, you may need to tweak the configuration file (see below) accordingly.
There is a .tar.gz of a complete genie install available from the releases, to right. As a last resort, you can try untarring this (it contains every needed file, with the correct permissions, in the correct path from /) onto your system while root. Don't do this unless you're confident you know what you're doing, you're willing to go looking for any resulting issues yourself, and you aren't afraid of accidentally breaking things. You will need to install the dependencies listed above beforehand.
We're actively looking for maintainers for everything that doesn't have a specific package. If you have the time, please contribute.
I am unable to support distributions which there are not prebuilt packages for. I am actively seeking maintainers for these packages.
That would be the file /etc/genie.ini. This defines the secure path (i.e., those directories in which genie will look for the utilities it depends on; make sure unshare, in particular, is available here), and seven settings controlling genie behavior. Normally, it looks like this:
[genie]
secure-path=/lib/systemd:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
update-hostname=true
update-hostname-suffix=-wsl
clone-path=false
clone-env=WSL_DISTRO_NAME,WSL_INTEROP,WSLENV,DISPLAY,WAYLAND_DISPLAY,PULSE_SERVER
systemd-timeout=240
resolved-stub=false
target-warning=true
The secure-path setting should be generic enough to cover all but the weirdest Linux filesystem layouts, but on the off-chance that yours stores binaries somewhere particularly idiosyncratic, you can change it here.
The update-hostname setting controls whether or not genie updates the WSL hostname when creating the bottle. By default, genie updates a hostname foo to foo-wsl, to prevent hostname clashes between the host Windows machine and the WSL distribution, especially when communicating back and forth between the two.
However, as recent WSL builds allow the hostname of the WSL distributions to be set in .wslconfig, this option has been provided to disable genie's intervention and keep the original hostname. Additionally, the update-hostname-suffix setting allows you to change the suffix added to the original hostname to create the WSL hostname.
HOWEVER if you are using bridged networking, which uses separate IP addresses for WSL, often acquired via DHCP, we strongly recommend not disabling this feature. On many networks, acquiring an address for WSL via DHCP with the same hostname as your Windows machine will remove your Windows machine's IP address from DNS, with irritatingly vague consequences.
The clone-path setting controls whether the PATH outside the bottle should be cloned inside the bottle. This can be useful since the outside-bottle path may include system-specific directories not mentioned in secure-path, and since the outside-bottle path includes a transformed version of the host machine's Windows path.
If this is set to true, the inside-bottle path will be set to the secure-path combined with the outside-bottle path, with duplicate entries removed. It is set to false by default, for backwards compatibility.
The clone-env setting lists the environment variables which are copied from outside the bottle to inside the bottle. It defaults to only WSL_DISTRO_NAME, WSL_INTEROP, and WSLENV, needed for correct WSL operation, plus DISPLAY, WAYLAND_DISPLAY, and PULSE_SERVER, needed for WSLg but any other environment variables which should be cloned can be added to this list.
The systemd-timeout setting controls how long (the number of seconds) genie will wait when initializing the bottle for systemd to reach its "running" - i.e. fully operational, with all units required by the default target active - state. This defaults to 240 seconds.
genie (1.44+) provides the resolved-stub option to automatically back up the existing /etc/resolv.conf and replace it with the symlink necessary to run systemd-resolved in stub mode when initializing the bottle, and revert to the backup when the bottle terminates. (NOTE: This last is a courtesy and should NOT be interpreted as meaning idempotency is supported in any way; see BUGS .) 1.43 performed this action by default; upgraders from 1.43 who wish to retain this behavior must set resolved-stub=true in the configuration file.
By default, genie (2.0+) warns you upon bottle initialization if the default systemd target is not multi-user.target, since this is the default with which genie is designed to work. If you have configured a different systemd target to run correctly with genie, this warning can be disabled by setting target-warning to false in the config file.
genie (1.39+) also installs a pair of systemd units (wslg-xwayland.service and wslg-xwayland.socket and an override for user-runtime-dir@.service) to ensure that WSLg operates correctly from inside the bottle. If desired, these can be disabled and enabled independently of genie itself.
usage: genie [-h] [-V] [-v] [-a USER] (-i | -s | -l | -c ... | -u | -r | -b)
Handles transitions to the "bottle" namespace for systemd under WSL.
optional arguments:
-h, --help show this help message and exit
-V, --version show program's version number and exit
-v, --verbose display verbose progress messages
-a USER, --as-user USER
specify user to run shell or command as (use with -s or -c)
commands:
-i, --initialize initialize the bottle (if necessary) only
-s, --shell initialize the bottle (if necessary), and run a shell in it
-l, --login initialize the bottle (if necessary), and open a logon prompt in it
-c ..., --command ...
initialize the bottle (if necessary), and run the specified command in it
-u, --shutdown shut down systemd and exit the bottle
-r, --is-running check whether systemd is running in genie, or not
-b, --is-in-bottle check whether currently executing within the bottle, or not
For more information, see https://github.com/arkane-systems/genie/
So, it has four modes, all of which will set up the bottle and run systemd in it if it isn't already running for simplicity of use.
genie -i will set up the bottle, run systemd, and then exit. This is intended for use if you want services running all the time in the background, or to preinitialize things so you needn't worry about startup time later on, and for this purpose is ideally run from Task Scheduler on logon.
NOTE: It is never necessary to run genie -i explicitly; the -s, -l, and -c commands will all set up the bottle if it has not already been initialized.
NOTE 2: genie -i DOES NOT enter the bottle for you. It is important to remember that the genie bottle functions like a container, with its own cgroups and separate pid and mount namespaces. While some systemd or systemd-service powered things may work when invoked from outside the bottle, this is ENTIRELY BY CHANCE, and is NOT A SUPPORTED SCENARIO. You must enter the bottle using genie -s, genie -l or genie -c first. Ways to do this automatically when you start a WSL session can be found on the repo wiki.
genie -s runs your login shell inside the bottle; basically, Windows-side, wsl genie -s is your substitute for just wsl to get started, or for the shortcut you get to start a shell in the distro. It follows login semantics, and as such does not preserve the current working directory.
genie -c [command] runs command inside the bottle, then exits. The return code is the return code of the command. It follows sudo semantics, and so does preserve the cwd.
With either of the above, the genie -a [user] option may be used to specify a particular user to start a shell for, or to run a command as, rather than using the currently logged-in user. For example, genie -a bongo -s would start a shell as the user bongo .
genie -l opens a login session within the bottle. This permits you to log in to the WSL distribution as any user. The login prompt will return when you log out; to terminate the session, press ^] three times within one second. It follows login semantics, and as such does not preserve the current working directory.
Meanwhile, genie -u , run from outside the bottle, will shut down systemd cleanly and exit the bottle. This uses the systemctl poweroff command to simulate a normal Linux system shutting down. It is suggested that this be used before shutting down Windows or restarting the Linux distribution to ensure a clean shutdown of systemd services.
NOTE 3: genie is not and cannot be idempotent. As such, it is strongly recommended that you do not restart genie or continue to use the WSL distro session after using genie -u. See BUGS, below.
genie -r and genie -b are informational commands for use in checking the state of the system and/or scripting genie.
The former checks whether genie (and an associated systemd(1) instance) are currently running. Possible output and return codes are:
- running (exit code 0) - the bottle (and systemd) are running normally
- stopped (exit code 1) - no bottle is present
- starting (exit code 2); and
- stopping (exit code 3) - the bottle is transitioning between states, please wait
- running (systemd errors) (exit code 4) - the bottle is up but some systemd services are reporting errors
- unknown (exit code 5) - unable to determine bottle state
The latter, meanwhile, checks whether the current command is executing inside the bottle. Possible output and return codes are:
- inside (exit code 0) - inside the bottle
- outside (exit code 1) - outside the bottle (bottle exists)
- no-bottle (exit code 2) - no bottle is present
While running, genie stores the external PID of the systemd instance in the file /run/genie.systemd.pid for use in user scripting. It does not provide a similar file for the internal PID for obvious reasons.
While not compulsory, it is recommended that you shut down and restart the WSL distro before using genie again after you have used genie -u. See BUGS, below, for more details.
If genie (1.31+) seems to be blocked at the
"Waiting for systemd...!!!!!"
stage, this is because of the new feature in 1.31 that waits for all systemd services/units to have started up before continuing, to ensure that they have started before you try and do anything that might require them. (I.e., it waits for the point at which a normal Linux system would have given you a login prompt.) It does this by waiting for systemd to reach the "running" state.
If it appears to have blocked, wait until the timeout (by default, 240 seconds), at which point a list of units which have not started property will be displayed. Fixing or disabling those units such that systemd can start properly will also allow genie to start properly. Known-problematic units are listed on the genie wiki.
Once you have this up and running, I suggest disabling via systemctl the getty@tty1 service (since logging on and using WSL is done via ptsen, not ttys).
Further tips on usage from other genie users can be found on the wiki for this repo.
-
It is considerably clunkier than I'd like it to be, inasmuch as you have to invoke genie every time to get inside the bottle, either manually (replacing, for example, wsl [command] with wsl genie -c [command]), or by using your own shortcut in place of the one WSL gives you for the distro, using which will put you outside the bottle. Pull requests, etc. But see also RunInGenie!
-
genie is not idempotent; i.e., it is possible that changes made by genie or by systemd inside the bottle will not be perfectly reverted when the genie bottle is shut down with genie -u . (Linux pid/mount namespaces aren't perfect containers, and systemd units and other actions inside the bottle can and will change things that affect the outside of the bottle, possibly even across distros. And note that genie -u calls systemctl poweroff which believes that it is shutting down the entire machine; the in-bottle systemd is a full systemd installation, not a cut-down container install.) As such, it is strongly recommended that you terminate the entire wsl session with wsl -t or wsl --shutdown in between stopping and restarting the bottle, or errors may occur; we cannot support such scenarios.
-
As of 1.38, while WSLg operates correctly with genie and GUI apps can be run from inside the bottle, Linux GUI apps started from the Windows Start Menu items created by WSLg will run outside the bottle. This is being worked on.
For information on versions of genie prior to 2.0, see the saved older README-1.44.md file in this repository.
