nix-community / nixbox

NixOS Vagrant boxes [maintainer=@ifurther]

Home Page:https://app.vagrantup.com/nixbox/

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Packer failing

Moredread opened this issue · comments

Running packer on Windows fails

    virtualbox-iso: building path(s) ‘/nix/store/1yhdxv73pz31xc9qb7184js1m2wzwjjb-sudoers’
    virtualbox-iso: >>> /nix/store/i8534j6r4mhw19aixas5g2ah4r17vx6x-sudoers-in: syntax error near line 18 <<<
    virtualbox-iso: >>> /nix/store/i8534j6r4mhw19aixas5g2ah4r17vx6x-sudoers-in: syntax error near line 24 <<<
    virtualbox-iso: >>> /nix/store/i8534j6r4mhw19aixas5g2ah4r17vx6x-sudoers-in: syntax error near line 25 <<<
    virtualbox-iso: parse error in /nix/store/i8534j6r4mhw19aixas5g2ah4r17vx6x-sudoers-in near line 18
    virtualbox-iso: builder for ‘/nix/store/97d6mb47w9gvy80hiink67x3a0z1cpnx-sudoers.drv’ failed with exit code 1
    virtualbox-iso: cannot build derivation ‘/nix/store/qr9y5na2xr9x655hl3s68g0xf66lm0q1-etc.drv’: 1 dependencies couldn't be built
    virtualbox-iso: building path(s) ‘/nix/store/9cj3shisi6yh1kbhrlgjwl1lcw0hy6d2-users-groups.json’
    virtualbox-iso: cannot build derivation ‘/nix/store/0bs048837g4fippjxb211n9wb5hbxql6-nixos-system-nixbox-17.09.2853.b222a0713f4.drv’: 1 dependencies couldn't be built
    virtualbox-iso: error: build of ‘/nix/store/0bs048837g4fippjxb211n9wb5hbxql6-nixos-system-nixbox-17.09.2853.b222a0713f4.drv’ failed
==> virtualbox-iso: Deregistering and deleting VM...
==> virtualbox-iso: Deleting output directory...
Build 'virtualbox-iso' errored: Script exited with non-zero exit status: 100

==> Some builds didn't complete successfully and had errors:
--> virtualbox-iso: Script exited with non-zero exit status: 100

==> Builds finished but no artifacts were created.

maybe try looking at the generated config to see if it contains windows line endings or not. I don't have a Windows machine handy.

Oh that could be an issue. I'll look at that later.

Yeah that's what is going on here. There was a previous issue, #15, which referenced this same log.

Might be worth putting a note in the readme to help users avoid this pitfall as it's pretty hard to tell what's going on when it happens.