[Nix-dev] NixOps on VServer (update)

[Bas van Dijk]

Are you deploying to a Hetzner VServer by any chance?

If that's the case, you probably want to use the following deployment
configuration:

deployment = {
  targetEnv = "hetzner";
  hetzner = {
    mainIPv4 = "X.X.X.X";
    robotUser = "XXXX";
    partitions = ''
      clearpart --all --initlabel --drives=sda
      part swap --recommended --label=swap --fstype=swap --ondisk=sda
      part / --fstype=ext4 --label=root --grow --ondisk=sda
    '';
  };
};

Also note that I have the following listed in my Hetzner configurations:

# TODO: These options are only needed when deploying to a
# Hetzner machine for the first time. After the initial deployment these
options
# should be commented. We should report this as a bug of nixops.
# boot.loader.grub.device = "/dev/sda";
# fileSystems."/" = {
#   device = "/dev/disk/by-label/root";
#   fsType = "ext4";
# };

Bas


On 28 March 2017 at 01:21, <mb at thought2.de> wrote:

> Here are more details to my previous message:
>
> I'm getting the following error, when deploying this
> (http://lpaste.net/353990) config to a remote nix machine:
>
> nixops deploy -d network
> building all machine configurations...
> error:
> Failed assertions:
> - The ‘fileSystems’ option does not specify your root file system.
> - You must set the option ‘boot.loader.grub.devices’ or
> 'boot.loader.grub.mirroredBoots' to make the system bootable.
> (use ‘--show-trace’ to show detailed location information)
> error: unable to build all machine configurations
>
> Does anybody have an idea how to fix this?
>
> _______________________________________________
> nix-dev mailing list
> nix-dev at lists.science.uu.nl
> http://lists.science.uu.nl/mailman/listinfo/nix-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.science.uu.nl/pipermail/nix-dev/attachments/20170328/d44c18f7/attachment.html>