| 24 Jun 2024 |
matthewcroughan | thank you for cleaning up after me | 13:24:38 |
alina🏳️⚧️🐾 | In reply to @lassulus:lassul.us a better documentation would have indeed been better for that option. but it's kernel modules which are available for the vm builder. so one can add bcachefs or zfs there or something like that i see, thank you | 13:25:36 |
lassulus | matthewcroughan: https://github.com/nix-community/disko/pull/685 | 13:26:43 |
alina🏳️⚧️🐾 | i'm reading the source code to see if what i'm currently coding is too similar from an architectual perspective and if it wouldn't be better to just create a PR, so more stupid questions may arise if that's okay :p | 13:27:47 |
lassulus | sure | 13:29:09 |
matthewcroughan | In reply to @alina:kescher.at i'm reading the source code to see if what i'm currently coding is too similar from an architectual perspective and if it wouldn't be better to just create a PR, so more stupid questions may arise if that's okay :p If the module option is improperly named or is in the wrong place, please suggest something else, would love it | 13:31:16 |
| 25 Jun 2024 |
| axiomss joined the room. | 22:06:24 |
| 27 Jun 2024 |
colemickens | hi yall, I'm trying to use a Hetzner volume for nix+home, but when I do this, it breaks nixos-anywhere: https://github.com/colemickens/nixcfg/commit/905507248b37c782a69d7fbd1ab1509e750b743b | 02:34:54 |
colemickens | any advice? | 02:34:56 |
colemickens | machine will boot into nixos in 6s...
+ echo machine will boot into nixos in 6s...
+ test -e /dev/kmsg
+ exec
Warning: Permanently added '94.130.73.187' (ED25519) to the list of known hosts.
Warning: Permanently added '94.130.73.187' (ED25519) to the list of known hosts.
ssh: connect to host 94.130.73.187 port 22: Connection timed out
ssh: connect to host 94.130.73.187 port 22: No route to host
and it just repeats the last line forever
| 02:35:19 |
colemickens | If I don't enable disk2, the naive regular hetzner nixos-anywhere deploy seems to work fine. | 02:35:35 |
colemickens | (fixing disk2.content.partitions."nix".name doesn't seem to fix it) | 02:42:48 |
colemickens | does disko have an idempotent mode of operation? I want to use it with nixos-anywhere to have ephemeral hetzner instances with a persistent volume | 04:29:36 |
colemickens | initial tests indicates that disko seems to happily just reformat the persistent disk :/ | 04:29:48 |
colemickens | surely there must be a "skipFormat" option i can set for subsequent deploys after initial setup, right? | 04:30:11 |
lassulus | The formatScript should be idempotent | 06:01:12 |
colemickens | lassulus: can you say more? When I deploy a Hetzner box with an attached disk, run nixos-anywhere, write a file into my /home, and then repeat the process, the /home is wiped and fresh. | 15:51:49 |
lassulus | yes, nixos-anywhere runs the diskoScript | 15:55:06 |
lassulus | that one runs the deactivate-disk script, this one destroys the disk | 15:55:19 |
lassulus | just running the formatScript output from disko would not kill the disk | 15:55:32 |
colemickens | I wonder how hard it would be to hack at nixos-anywhere to give it a flag to skip the deactive-disk. | 16:32:22 |
lassulus | should be already possible, you are using flakes I guess? you could say something like:
system.build.diskoScript = lib.mkForce (pkgs.writeScriptBin "disko-without-wipe" ''
${config.system.build.formatScript}
${config.system.build.mountScript}
'');
| 16:37:09 |
lassulus | btw, why are you running nixos-anywhere again? | 16:37:24 |
lassulus | you can also just use nixos-rebuild --target-host | 16:37:40 |
colemickens | lassulus: I want to tear down the Hetzner machines when I'm not using them. The goal is to have /nix and /home on a volume. So I can recreate server, re-run nixos-anyhwere, and have /nix and /home (and maybe /etc, I guess) restored. | 16:38:56 |
colemickens | In reply to @lassulus:lassul.us
should be already possible, you are using flakes I guess? you could say something like:
system.build.diskoScript = lib.mkForce (pkgs.writeScriptBin "disko-without-wipe" ''
${config.system.build.formatScript}
${config.system.build.mountScript}
'');
nice, thanks. | 16:38:57 |
lassulus | the script was not tested, but I hope you get the idea :) | 16:39:19 |
| 28 Jun 2024 |
| axiomss left the room. | 04:13:09 |
magic_rb | i wanted to ask: on systems with a MBR parttable i keep getting the warning about it being deprecated and from what i read on the github page of disko, the path forward is to switch to GPT, but i have at least one system where that is impossible and multiple where switching it right now would be very very impractical. Is MBR supported some other way or are you just deprecating support for it completely? | 06:26:53 |
lassulus | Mostly dropping completly. There are hybrid tables in GPT. And I haven't seen a usecase where they don't work | 07:05:41 |