534a01c2b0
curl does not retry if it is unable to connect to the metadata server. For some reason, when creating a new AMI with a recent nixpkgs, the metadata server would not be available when fetch-ec2-data ran. Switching to wget that can retry even on TCP connection errors solved this problem. I also made the fetch-ec2-data depend on ip-up.target, to get it to start a bit later. |
||
---|---|---|
.. | ||
amazon-config.nix | ||
amazon-image.nix | ||
container-config.nix | ||
containers.nix | ||
docker.nix | ||
ec2-data.nix | ||
google-compute-config.nix | ||
google-compute-image.nix | ||
libvirtd.nix | ||
nixos-container.pl | ||
nova-config.nix | ||
nova-image.nix | ||
nova.nix | ||
qemu-opts | ||
qemu-vm.nix | ||
virtualbox-guest.nix | ||
virtualbox-image.nix | ||
xen-dom0.nix | ||
xen-domU.nix |