| 9 Dec 2022 |
 @andreas.schraegle:helsinki-systems.de | theoretically, you should be able to do what the NixOS module does manually/with whatever config management tool you use. I agree with Linux Hackerman tho. It sounds painful. | 09:35:54 |
 terwiz | Ouch. Well, the server is in AWS and NixOS was not on the premade image list (surprise, surprise). and the server is up and running already. This setup was/is just fine for doing manual builds, and those are still happening, so can't just reinstall everything.
With dockerized hydra I suppose the main issue was the /nix/store setup. Also, the nixos/hydra docker image is actually ubuntu + nix and not nixos. So I was also finding it difficult to configure, as all the instructions are for setting etc/nixos/configuration.nix and you don't have that in ubuntu + nix. That's also why I asked for pointers to docs, I expect the same issue without the docker... | 11:23:38 |
 @linus:schreibt.jetzt | In reply to @terwiz:matrix.org
Ouch. Well, the server is in AWS and NixOS was not on the premade image list (surprise, surprise). and the server is up and running already. This setup was/is just fine for doing manual builds, and those are still happening, so can't just reinstall everything.
With dockerized hydra I suppose the main issue was the /nix/store setup. Also, the nixos/hydra docker image is actually ubuntu + nix and not nixos. So I was also finding it difficult to configure, as all the instructions are for setting etc/nixos/configuration.nix and you don't have that in ubuntu + nix. That's also why I asked for pointers to docs, I expect the same issue without the docker... The NixOS foundation publishes NixOS AMIs though | 12:17:49 |
| @linus:schreibt.jetzt | But if you've got it working then 🤷 | 12:18:38 |
| 10 Dec 2022 |
|  @rimuru:gentoo.chat changed their profile picture. | 00:27:50 |
| 11 Dec 2022 |
 vcunat | 🤔 Hydra.nixos.org is now sometimes throwing eval errors like
{UNKNOWN}: aggregate job ‘tested’ failed with the error: nixos.tests.installer.swraid.x86_64-linux: error: cannot connect to socket at '/nix/var/nix/gc-socket/socket': No such file or directory
at /nix/store/j96zrgb48aiwxysh1vhq1zp1zv4da29r-hydra-perl-deps/lib/perl5/site_perl/5.34.1/Catalyst/Model/DBIC/Schema.pm line 526
| 09:44:27 |
| vcunat | Maybe #infra:nixos.org would be a better channel; I'm not sure. | 09:44:56 |
| vcunat | Retrying evaluation seems to fix it so far, but that can get annoying in the big jobsets where eval can take roughly an hour. | 09:45:58 |
| 12 Dec 2022 |
 jackdk | In reply to @terwiz:matrix.org
Ouch. Well, the server is in AWS and NixOS was not on the premade image list (surprise, surprise). and the server is up and running already. This setup was/is just fine for doing manual builds, and those are still happening, so can't just reinstall everything.
With dockerized hydra I suppose the main issue was the /nix/store setup. Also, the nixos/hydra docker image is actually ubuntu + nix and not nixos. So I was also finding it difficult to configure, as all the instructions are for setting etc/nixos/configuration.nix and you don't have that in ubuntu + nix. That's also why I asked for pointers to docs, I expect the same issue without the docker... aws ec2 describe-images --filters Name=owner-id,Values=080433136561 lists all amis published by the nixos org | 11:39:15 |
|  Tom Purl (he/him) joined the room. | 15:52:13 |
| 13 Dec 2022 |
|  Piper (she/they) changed their display name from pmc to Piper (she/they). | 22:59:47 |
| 14 Dec 2022 |
|  @nahfe:nahfe.xyz changed their display name from NAHFE to Herman. | 10:53:43 |
|  Alesya joined the room. | 11:15:18 |
| @nahfe:nahfe.xyz changed their display name from Herman to NAHFE. | 11:30:39 |
| @nahfe:nahfe.xyz changed their display name from NAHFE to Herman. | 11:32:58 |
