samueldr changed the topic of #nixops to: NixOps related talk | logs: https://logs.nix.samueldr.com/nixops/
abathur has quit [Ping timeout: 256 seconds]
nuncanada3 has quit [Ping timeout: 255 seconds]
johnny101 has quit [Ping timeout: 240 seconds]
nuncanada3 has joined #nixops
abathur has joined #nixops
abathur has quit [Ping timeout: 240 seconds]
nuncanada3 has quit [Ping timeout: 240 seconds]
abathur has joined #nixops
mtjmullen has joined #nixops
mutantmell has quit [*.net *.split]
aminechikhaoui has joined #nixops
abathur has quit [Ping timeout: 268 seconds]
abathur has joined #nixops
abathur has quit [Ping timeout: 260 seconds]
abathur has joined #nixops
abathur has quit [Ping timeout: 260 seconds]
nuncanada3 has joined #nixops
abathur has joined #nixops
abathur has quit [Ping timeout: 240 seconds]
lordcirth_ has joined #nixops
<lordcirth_> pxe> warning: unable to download 'https://cache.nixos.org/1fsn9bvnvj8sv7v39pw4cvl1s30jdmrx.narinfo': Couldn't resolve host name (6); retrying in 295 ms
<lordcirth_> Yet host cache.nixos.org works perfectly?
<lordcirth_> Maybe an IPv6 problem?
<adisbladis> gchristensen: ^
<adisbladis> Hmmmm
<lordcirth_> Oh, wait, the failure is happening *inside* the managed machine. I thought NixOps builds everything locally and copies it over?
<lordcirth_> systemd-resolve isn't running on the target
<lordcirth_> Unit systemd-resolve.service could not be found.
<adisbladis> I wonder if there is a good reason not to enable resolved by default
<lordcirth_> Oh, I assumed it was the default resolver in NixOS
abathur has joined #nixops
<lordcirth_> Ah ok, I added stuff to dnsmasq and probably broke it
nuncanada2 has joined #nixops
nuncanada3 has quit [Ping timeout: 258 seconds]
abathur has quit [Ping timeout: 255 seconds]