Inconsistency between linux and mac + remote linux builder

[svniemeijer]

I got the remote linux builder for mac to work using https://github.com/LnL7/nix-docker and the hints mentioned in #560 (i.e. adding nixpkgs.localSystem.system = "x86_64-linux"; to the network configuration for the host and not using --option system x86_64-linux). Which is great!

However, I am not getting the same results when I build the same system on a linux host vs. building it with the remote linux docker builder from macos.

The problem seems to be in an inconsistency with a nix options file that is used to generate nixos documentation that gets included in the overall nixos deployment:

Difference in options.xml:

--- /nix/store/ba64dcv6xvair0182rvs336yacmiqawa-options.xml	1970-01-01 01:00:01.000000000 +0100
+++ /nix/store/r64z1lckd848jzvsdm4vbnrhh8a2dwa2-options.xml	1970-01-01 01:00:01.000000000 +0100
@@ -24949,7 +24949,7 @@
       <attr name="default">
         <attrs>
           <attr name="system">
-            <string value="x86_64-darwin" />
+            <string value="x86_64-linux" />
           </attr>
         </attrs>
       </attr>

nix why-depends on mac + builder:

/nix/store/6dv7clzkb532qrzj8alpripag5mlny83-nixos-system-valse-18.09.1023.06fb0253afa.drv
╚═══/: …2.25.drv",["out"]),("/nix/store/4bjph24kcwnld5z7chs90my7k5l5nhmz-system-path.drv",["out"]),("/ni…
    => /nix/store/4bjph24kcwnld5z7chs90my7k5l5nhmz-system-path.drv
    ╚═══/: …2.27.drv",["bin"]),("/nix/store/s9hivgi2h47ygvz5xsg97zifhxjrinjg-nixos-manpages.drv",["out"]),("…
        => /nix/store/s9hivgi2h47ygvz5xsg97zifhxjrinjg-nixos-manpages.drv
        ╚═══/: …inux.drv",["out"]),("/nix/store/kfl49k52jw17hp87kpyv2y1873vjsjqk-nixos-manual-combined.drv",["ou…
            => /nix/store/kfl49k52jw17hp87kpyv2y1873vjsjqk-nixos-manual-combined.drv
            ╚═══/: …-p23.drv",["out"]),("/nix/store/zssy4rskn36vc37y5595yafkkycqvnv3-generated-docbook.drv",["out"])…
                => /nix/store/zssy4rskn36vc37y5595yafkkycqvnv3-generated-docbook.drv
                ╚═══/: …-docbook","","")],[("/nix/store/1bywipg4sy5z5mfc3f90yyy0y7r2987f-options-db.xml.drv",["out"]),("…
                    => /nix/store/1bywipg4sy5z5mfc3f90yyy0y7r2987f-options-db.xml.drv
                    ╚═══/: …default-builder.sh","/nix/store/ba64dcv6xvair0182rvs336yacmiqawa-options.xml","/nix/store/lv2yhh…
                        => /nix/store/ba64dcv6xvair0182rvs336yacmiqawa-options.xml

nix why-depends on linux:

/nix/store/3ll6l59192hn9wsdn42d383i99fgav3q-nixos-system-valse-18.09.1023.06fb0253afa.drv
╚═══/: …2.27.drv",["bin"]),("/nix/store/syl72xqrdznwkr4v2358sc2scdfks1wm-system-path.drv",["out"]),("/ni…
    => /nix/store/syl72xqrdznwkr4v2358sc2scdfks1wm-system-path.drv
    ╚═══/: …0.11.drv",["out"]),("/nix/store/8q11mf0g50p19q2pnrz0nmvga2ng5n6n-nixos-manual.drv",["out"]),("/n…
        => /nix/store/8q11mf0g50p19q2pnrz0nmvga2ng5n6n-nixos-manual.drv
        ╚═══/: …s-manual","","")],[("/nix/store/1fs4wgsx8cq7jdhbi5mc4fgxgy6aj7na-nixos-manual-combined.drv",["ou…
            => /nix/store/1fs4wgsx8cq7jdhbi5mc4fgxgy6aj7na-nixos-manual-combined.drv
            ╚═══/: …-p23.drv",["out"]),("/nix/store/yj3b5520l9hd33h92r1lbkxdg6mdwfd2-generated-docbook.drv",["out"])…
                => /nix/store/yj3b5520l9hd33h92r1lbkxdg6mdwfd2-generated-docbook.drv
                ╚═══/: …-docbook","","")],[("/nix/store/bddnpfxxsx0xyh7fp6p52dlplx0fpn4i-options-db.xml.drv",["out"]),(>
                    => /nix/store/bddnpfxxsx0xyh7fp6p52dlplx0fpn4i-options-db.xml.drv
                    ╚═══/: …ons-to-docbook.xsl","/nix/store/r64z1lckd848jzvsdm4vbnrhh8a2dwa2-options.xml"],"x86_64-linu>
                        => /nix/store/r64z1lckd848jzvsdm4vbnrhh8a2dwa2-options.xml

I am not sure whether this is the right issue tracker to post this (since it looks more like a 'channel' issue), but it is very much related to #560.

[svniemeijer]

I am no longer seeing this inconsistency, so I am closing the issue.