Closed ianmjones closed 5 years ago
@ianmjones Oops. I noticed that my script had bitrotted a few months ago but never updated it. With newer setup it needs some changes but I don't remember what they were.
One thing I recall running into was that if using multi-user nix you need the nix daemon to access the docker container. This means you need root
to have access to the identity files. When I was toying with this, there was no way to tell nix to use different SSH configuration for remote builders.
Thanks @3noch, but I don't think it's related to running multi-user nix as I'm not doing so (any more, I uninstalled nix and re-installed the now non-multi-user by default on Mac version a few days ago).
I did a bunch of experiments and tests and found that it was purely down to the quotes surrounding the identity file name as generated by the start-docker-nix-build-slave
script.
First off, thank you very much for building this project @LnL7, and for making it so easy to use as a remote builder @3noch with the addition of the
start-docker-nix-build-slave
script.On macOS 10.12.6 I was able to do the following...
start-docker-nix-build-slave
.export NIX_REMOTE_SYSTEMS="$HOME/.nix-docker-build-slave/remote-systems.conf"
to set my current shell to use the docker container as a remote builder..profile
for later use...Then successfully used
nixops create ...
andnixops deploy ...
on the nixops load-balancer example to create a virtualbox network. (the usual fail on first virtualbox deploy requiringnixops stop / start / deploy
was expected)However, during the deploy every build command was followed up by a warning about the identity file not being available, is that due to something I did wrong, or something that could be improved?
I think the file it's complaining about is in the right place etc..