!9IQChSjwSHXPPWTa:lix.systems

Lix

1101 Members
Lix user channel. Feel free to discuss on-topic issues here and give each other help. For matrix.to links to the rest of the Lix channels, see: https://wiki.lix.systems/books/lix-organisation/page/matrix-rooms293 Servers

Load older messages

SenderMessageTime
2 Dec 2025
@raitobezarius:matrix.orgraitobezarius https://git.lix.systems/lix-project/lix/issues/485 22:10:20
@raitobezarius:matrix.orgraitobezariusit's part of 2.95 milestone22:10:26
@raitobezarius:matrix.orgraitobezarius that is, --rebuild/--check will automatically produce the first derivation from now on and perform the check right after 22:10:41
@raitobezarius:matrix.orgraitobezarius(this is independent from the naming discussions on which I think I agree)22:11:31
@raitobezarius:matrix.orgraitobezariusinteresting22:12:37
@raitobezarius:matrix.orgraitobezariusi feel like we don't have an issue for it22:12:42
@raitobezarius:matrix.orgraitobezariusi feel like the generalized flag for this idea one that uses the deriver concept22:14:28
@raitobezarius:matrix.orgraitobezarius nix-build --requires-deriver local or something 22:14:41
@xoredg:matrix.orgxored

can someone explain to me why lix is this weird? ```[root@shiva:~]# cat /etc/resolv.conf

This is /run/systemd/resolve/stub-resolv.conf managed by man:systemd-resolved(8).

Do not edit.

This file might be symlinked as /etc/resolv.conf. If you're looking at

/etc/resolv.conf and seeing this text, you have followed the symlink.

This is a dynamic resolv.conf file for connecting local clients to the

internal DNS stub resolver of systemd-resolved. This file lists all

configured search domains.

Run "resolvectl status" to see details about the uplink DNS servers

currently in use.

Third party programs should typically not access this file directly, but only

through the symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a

different way, replace this symlink by a static file or a different symlink.

See man:systemd-resolved.service(8) for details about the supported modes of

operation for /etc/resolv.conf.

nameserver 127.0.0.53
options edns0 trust-ad
search .

[root@shiva:~]# nix-build -E '(import <nixpkgs> {}).runCommand "test" {outputHashMode = "recursive"; outputHash = "sha256-AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA=";} "cat /etc/resolv.conf"'
this derivation will be built:
/nix/store/qnd72abhlx97l63pppg9n23nwcnm00fl-test.drv
building '/nix/store/qnd72abhlx97l63pppg9n23nwcnm00fl-test.drv'...

This is /run/systemd/resolve/stub-resolv.conf managed by man:systemd-resolved(8).

Do not edit.

This file might be symlinked as /etc/resolv.conf. If you're looking at

/etc/resolv.conf and seeing this text, you have followed the symlink.

This is a dynamic resolv.conf file for connecting local clients to the

internal DNS stub resolver of systemd-resolved. This file lists all

configured search domains.

Run "resolvectl status" to see details about the uplink DNS servers

currently in use.

Third party programs should typically not access this file directly, but only

through the symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a

different way, replace this symlink by a static file or a different symlink.

See man:systemd-resolved.service(8) for details about the supported modes of

operation for /etc/resolv.conf.

options edns0 trust-ad
search .

nameserver 169.254.1.1
nameserver 64:ff9b:1:4b8e:472e:a5c8:a9fe:0101```

apparently there's a thing called pasta and I saw some resolvconf rewrite in the code, whatever the case, if my host is ipv6 only I get no dns in the sandbox, looks like a bug

23:02:25
@niklaskorz:matrix.orgniklaskorzbig font time23:02:39
@xoredg:matrix.orgxored *

can someone explain to me why lix is this weird?

[root@shiva:~]# cat /etc/resolv.conf
# This is /run/systemd/resolve/stub-resolv.conf managed by man:systemd-resolved(8).
# Do not edit.
#
# This file might be symlinked as /etc/resolv.conf. If you're looking at
# /etc/resolv.conf and seeing this text, you have followed the symlink.
#
# This is a dynamic resolv.conf file for connecting local clients to the
# internal DNS stub resolver of systemd-resolved. This file lists all
# configured search domains.
#
# Run "resolvectl status" to see details about the uplink DNS servers
# currently in use.
#
# Third party programs should typically not access this file directly, but only
# through the symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a
# different way, replace this symlink by a static file or a different symlink.
#
# See man:systemd-resolved.service(8) for details about the supported modes of
# operation for /etc/resolv.conf.

nameserver 127.0.0.53
options edns0 trust-ad
search .

[root@shiva:~]# nix-build -E '(import <nixpkgs> {}).runCommand "test" {outputHashMode = "recursive"; outputHash = "sha256-AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA=";} "cat /etc/resolv.conf"'
this derivation will be built:
  /nix/store/qnd72abhlx97l63pppg9n23nwcnm00fl-test.drv
building '/nix/store/qnd72abhlx97l63pppg9n23nwcnm00fl-test.drv'...
# This is /run/systemd/resolve/stub-resolv.conf managed by man:systemd-resolved(8).
# Do not edit.
#
# This file might be symlinked as /etc/resolv.conf. If you're looking at
# /etc/resolv.conf and seeing this text, you have followed the symlink.
#
# This is a dynamic resolv.conf file for connecting local clients to the
# internal DNS stub resolver of systemd-resolved. This file lists all
# configured search domains.
#
# Run "resolvectl status" to see details about the uplink DNS servers
# currently in use.
#
# Third party programs should typically not access this file directly, but only
# through the symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a
# different way, replace this symlink by a static file or a different symlink.
#
# See man:systemd-resolved.service(8) for details about the supported modes of
# operation for /etc/resolv.conf.


options edns0 trust-ad
search .

nameserver 169.254.1.1
nameserver 64:ff9b:1:4b8e:472e:a5c8:a9fe:0101

apparently there's a thing called pasta and I saw some resolvconf rewrite in the code, whatever the case, if my host is ipv6 only I get no dns in the sandbox, looks like a bug

23:03:12
@niklaskorz:matrix.orgniklaskorzthanks :D23:03:18
@xoredg:matrix.orgxoredyeah I hate element's input man23:03:24
@xoredg:matrix.orgxoredtl;dr on the sandbox the dns is all messed up23:03:42
@xoredg:matrix.orgxoredI have an ipv6 only host and dns64 running on my network23:03:53
@xoredg:matrix.orgxoredthe host resolves just fine, but when I build anything through the sandbox I can't download anything23:04:11
@niklaskorz:matrix.orgniklaskorzit's described in the Lix 2.94 release notes23:04:23
@niklaskorz:matrix.orgniklaskorzhttps://lix.systems/blog/2025-11-18-lix-2.94-release/23:04:28
@niklaskorz:matrix.orgniklaskorzit only picks up the first entry in your dns resolv apparently23:04:50
@niklaskorz:matrix.orgniklaskorz* it only picks up the first entry in your dns resolv.conf apparently23:05:17
@xoredg:matrix.orgxoredhmmmm I'm using systemd-resolved23:05:30
@xoredg:matrix.orgxoredthere's only one entry23:05:36
@xoredg:matrix.orgxoredI think it's doing something "not clever"23:05:52
@xoredg:matrix.orgxoredso apparently the v6 address is also a nat64 for 169.254.1.123:07:16
@xoredg:matrix.orgxoredwhat on earth is lix doing man23:07:23
@raitobezarius:matrix.orgraitobezariusthis is pasta23:07:32
@raitobezarius:matrix.orgraitobezarius169.254.1.1 is connected to your host localhost23:07:43
@xoredg:matrix.orgxoredwell I choose Lix not pasta lmao23:07:52
@raitobezarius:matrix.orgraitobezarius https://docs.lix.systems/manual/lix/stable/advanced-topics/pasta.html 23:08:01
@raitobezarius:matrix.orgraitobezariusso you're saying with an IPv6-only system, you are still having a issue with DNS64/NAT64?23:08:18

Show newer messages

Back to Room ListRoom Version: 10