!apXxbtexmNGJaAryzM:nixos.org

NixOS on WSL

351 Members
https://github.com/nix-community/NixOS-WSL63 Servers

Load older messages


SenderMessageTime
17 Jan 2023
@ecmacat:matrix.orgecmacat
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:0upti.meK900Known issue with latest systemds11:55:58
@nzbr:nzbr.deArson 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:0upti.meK900Just use native systemd11:57:30
@k900:0upti.meK900Native systemd is considerably less broken 11:57:50
@ecmacat:matrix.orgecmacatThanks, this resolved my issue. (for those who wanna try this: after enabling nativeSystemd a full restart of wsl is required)12:04:35
@ecmacat:matrix.orgecmacatBefore the native systemd thing, did we just use the systemd provided by WSL?12:05:03
@k900:0upti.meK900No 12:05:11
@ecmacat:matrix.orgecmacatPlease correct me if I were wrong12:05:13
@k900:0upti.meK900"Native" here means using WSL's native systemd integration 12:05:26
@k900:0upti.meK900The default approach is to use container trickery to run systemd as not-actually-pid112:05:41
@ecmacat:matrix.orgecmacat
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:0upti.meK900Yes12:07:18
@ecmacat:matrix.orgecmacat set a profile picture.12:45:55
@jhillyerd:matrix.org@jhillyerd:matrix.org left the room.18:47:27
@nzbr:nzbr.deArson Copperflame Why exactly does this fix the tests on Windows for me? It makes no sense at all
https://github.com/nzbr/NixOS-WSL/commit/ce22a237d71c3c19de0bb0a69eb3b7d4f7880116
20:55:20
@nzbr:nzbr.deArson Copperflameimage.png
Download image.png
20:59:20
@nzbr:nzbr.deArson CopperflameIt doesn't help that the error message I got before that looks equally mysterious20:59:43
@k900:0upti.meK900Timing? 21:02:47
@k900:0upti.meK900 Try to stick a sleep 1 in there? 21:02:56
@nzbr:nzbr.deArson CopperflameRight not I'm rebuilding with it removed to make sure I'm not hallucinating or something21:03:48
@nzbr:nzbr.deArson CopperflameBut it's a good idea, i'll try that next21:04:23
@nzbr:nzbr.deArson Copperflame Since I made that commit, it somehow works even with the for ... echo $x removed... So maybe it was something external after all that got fixed by forcing nix to build a new tarball (either by changing a file or having a different git rev) 21:20:53
18 Jan 2023
@sandro:supersandro.deSandro 🐧Should we do a wsl maintainer team and put programs like wslu under it?13:12:57
@nzbr:nzbr.deArson CopperflameDo you mean in nixpkgs?14:15:19
@sandro:supersandro.deSandro 🐧yes14:56:08
@nzbr:nzbr.deArson CopperflameI guess you'd have to ask the maintainer of the wslu package, but I think it'd make sense16:06:01
19 Jan 2023
@k900:0upti.meK900Oh no07:54:53
@k900:0upti.meK900The latest preview update breaks us07:55:03
@k900:0upti.meK900I think they fixed /dev/shm07:55:08

Show newer messages


Back to Room ListRoom Version: 9