error: attribute 'config' in selection path 'config.system.build.toplevel' not found

[xyno-dev]

After building the image and flashing it onto a microsd card, the pi boots! It runs perfectly fine and ssh works as expected.
However, when I go to rebuild the config using nix run github:serokell/deploy-rs .#zero2w -- --ssh-user [username] --hostname [ip], I get the following error:

🚀 ℹ️ [deploy] [INFO] Running checks for flake in .
warning: Git tree '/home/nixyfedora/nixos-pi-zero-2' is dirty
error:
       … while checking flake output 'nixosConfigurations'
         at «github:numtide/flake-utils/11707dc2f618dd54ca8739b309ec4fc024de578b?narHash=sha256-l0KFg5HjrsfsO/JpG%2Br7fRrqm12kzFHyUHqHCVpMMbI%3D»/lib.nix:43:9:
           42|       // {
           43|         ${key} = (attrs.${key} or { }) // {
             |         ^
           44|           ${system} = ret.${key};

       … while checking the NixOS configuration 'nixosConfigurations.aarch64-linux'
         at «github:numtide/flake-utils/11707dc2f618dd54ca8739b309ec4fc024de578b?narHash=sha256-l0KFg5HjrsfsO/JpG%2Br7fRrqm12kzFHyUHqHCVpMMbI%3D»/lib.nix:44:11:
           43|         ${key} = (attrs.${key} or { }) // {
           44|           ${system} = ret.${key};
             |           ^
           45|         };

       error: attribute 'config' in selection path 'config.system.build.toplevel' not found
🚀 ❌ [deploy] [ERROR] Failed to check deployment: Nix checking command resulted in a bad exit code: Some(1)

I am not sure what is causing this at all, and am completely stumped. Probably because of my limited knowledge on flakes and deploy-rs.

[adingbatponder]

Thanks for posting this. I will do my best to try this out and of course let you know. Sent from [Proton Mail](https://proton.me/mail/home) for Android.

…

-------- Original Message --------

On Monday, 10/27/25 at 11:31 Xyno ***@***.***> wrote: Xyno-dev created an issue [(plmercereau/nixos-pi-zero-2#22)](#22) After building the image and flashing it onto a microsd card, the pi boots! It runs perfectly fine and ssh works as expected. However, when I go to rebuild the config using nix run github:serokell/deploy-rs .#zero2w -- --ssh-user [username] --hostname [ip], I get the following error: 🚀 ℹ️ [deploy] [INFO] Running checks for flake in . warning: Git tree '/home/nixyfedora/nixos-pi-zero-2' is dirty error: … while checking flake output 'nixosConfigurations' at «github:numtide/flake-utils/11707dc2f618dd54ca8739b309ec4fc024de578b?narHash=sha256-l0KFg5HjrsfsO/JpG%2Br7fRrqm12kzFHyUHqHCVpMMbI%3D»/lib.nix:43:9: 42| // { 43| ${key} = (attrs.${key} or { }) // { | ^ 44| ${system} = ret.${key}; … while checking the NixOS configuration 'nixosConfigurations.aarch64-linux' at «github:numtide/flake-utils/11707dc2f618dd54ca8739b309ec4fc024de578b?narHash=sha256-l0KFg5HjrsfsO/JpG%2Br7fRrqm12kzFHyUHqHCVpMMbI%3D»/lib.nix:44:11: 43| ${key} = (attrs.${key} or { }) // { 44| ${system} = ret.${key}; | ^ 45| }; error: attribute 'config' in selection path 'config.system.build.toplevel' not found 🚀 ❌ [deploy] [ERROR] Failed to check deployment: Nix checking command resulted in a bad exit code: Some(1) I am not sure what is causing this at all, and am completely stumped. Probably because of my limited knowledge on flakes and deploy-rs. — Reply to this email directly, [view it on GitHub](#22), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/AYHERH3T4RLOOWR2R2M5KZL3ZXQ77AVCNFSM6AAAAACKJ3OCLCVHI2DSMVQWIX3LMV43ASLTON2WKOZTGU2TMMJQGMYTGMQ). You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[Kansattica]

Having the same issue trying to deploy-rs from x86_64-linux (nix on Debian, not nixOS). I suspect it's something to do with the deploy being inside flake-utils.lib.eachDefaultSystem? Looks similar to https://discourse.nixos.org/t/using-deploy-rs-with-existing-configuration/31665/4

[plmercereau]

could you try bypassing deploy-rs checks in adding the --skip-checks flag?

[Kansattica]

--skip-checks gave me a different error about nodes, but I got it to work by commenting out flake-utils.lib.eachDefaultSystem and putting system = "x86_64-linux"; in the let. Obviously this isn't great for anyone not on x86_64-linux, but it worked for me.