| 17 Jan 2023 |
 ecmacat | I guess the documentation for NixOS-WSL is not quite complete? | 11:42:23 |
 K900 | What exactly are you missing? | 11:42:43 |
| ecmacat | For example, there's no explanation on the use of docker-native and docker-desktop | 11:42:46 |
| ecmacat | What's the difference between using docker-native and virtualisation.docker.enable | 11:43:10 |
 Arson Copperflame | docker-native is a wrapper around virtualisation.docker.enable that uses a patched docker derivation, because the original one will not work under WSL | 11:44:04 |
| Arson Copperflame | docker-desktop tries to set up a connection to Docker Desktop running on the Windows host, but it's a little flakey unfortunately | 11:45:54 |
| ecmacat | thanks for your information | 11:46:41 |
| ecmacat | The issue that docker-native tried to fix seems to be related to iptables? | 11:47:04 |
| Arson Copperflame | Yes, it needs to be compiled against iptables-legacy instead of the default iptables | 11:47:52 |
| ecmacat | thanks | 11:49:06 |
| ecmacat | Another problem related to systemd: I tried to upgrade to nixos-unstable, and several units failed:
● systemd-sysctl.service loaded failed failed Apply Kernel Variables
● systemd-tmpfiles-setup-dev.service loaded failed failed Create Static Device Nodes in /dev
● systemd-tmpfiles-setup.service loaded failed failed Create Volatile Files and Directories
| 11:52:47 |
| ecmacat | They are not needed in wsl anyway, so why aren't they masked? | 11:53:13 |
| ecmacat | * Another problem is related to systemd: I tried to upgrade to nixos-unstable, and several units failed:
● systemd-sysctl.service loaded failed failed Apply Kernel Variables
● systemd-tmpfiles-setup-dev.service loaded failed failed Create Static Device Nodes in /dev
● systemd-tmpfiles-setup.service loaded failed failed Create Volatile Files and Directories
| 11:53:26 |
| Arson Copperflame | Do those fail on 22.11 as well? | 11:53:45 |
| ecmacat | they don't | 11:54:01 |
| ecmacat | Failed to set up credentials: Protocol error
Failed at step CREDENTIALS spawning /nix/store/cgjjaqvxpq1z1a9bnxjvszjzvm93razf-systemd-252.4/lib/systemd/systemd-sysctl: Protocol error
| 11:54:42 |
| K900 | Known issue with latest systemds | 11:55:58 |
| Arson Copperflame | In reply to @ecmacat:matrix.org
Failed to set up credentials: Protocol error
Failed at step CREDENTIALS spawning /nix/store/cgjjaqvxpq1z1a9bnxjvszjzvm93razf-systemd-252.4/lib/systemd/systemd-sysctl: Protocol error
https://github.com/nix-community/NixOS-WSL/issues/185 | 11:56:26 |
| K900 | Just use native systemd | 11:57:30 |
| K900 | Native systemd is considerably less broken | 11:57:50 |
| ecmacat | Thanks, this resolved my issue. (for those who wanna try this: after enabling nativeSystemd a full restart of wsl is required) | 12:04:35 |
| ecmacat | Before the native systemd thing, did we just use the systemd provided by WSL? | 12:05:03 |
| K900 | No | 12:05:11 |
| ecmacat | Please correct me if I were wrong | 12:05:13 |
| K900 | "Native" here means using WSL's native systemd integration | 12:05:26 |
| K900 | The default approach is to use container trickery to run systemd as not-actually-pid1 | 12:05:41 |
| ecmacat | In reply to @k900:0upti.me
The default approach is to use container trickery to run systemd as not-actually-pid1 pid namespace thing? | 12:05:54 |
| K900 | Yes | 12:07:18 |
| ecmacat set a profile picture. | 12:45:55 |
|  @jhillyerd:matrix.org left the room. | 18:47:27 |
