Replies: 1 comment
|
The reason is explained here #145 (comment) Some assumptions about containers from NixOS side do not hold true for WSL. Like we need pam unlike for systemd-nspawn or we can load kernel modules or set sysctl values or change the rtc or create tun tap devices. So we are not going to set it again as it breaks things that are working in WSL. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
A user distro in WSL2 is effectively a container managed by the WSL
initprogram. There is an underlying CBL-Mariner system distro running in the root namespace.hostnamectlalso identifies theChassisattribute ascontainer.Given this, should we set
boot.isContainerto true? What are the pros and cons of doing so?Ref: #956 #957
I found #145 and #149 about this, but the underlying reason remains unclear to me.
The output of
ps afxin the WSL debug shell provides a reference for what is running in the root namespace:All reactions