Building AMIs is even simpler (and faster) with nixos-generators. The only remaining bit is to push them to a S3 bucket and get them registered on AWS.
Interesting project. How can it be simpler and faster if it’s calling the same amazon-image.nix module that nixpkgs provides? If I needed a single nix configuration upstream of several images (EC2, Azure, GCP, etc.) then it’s definitely worth considering. Otherwise, I think using packer to build atop the NixOS AMI is faster because you’re not making a disk image, then sending it to S3, then waiting for VM Import.
I will probably edit in a link to the nixos-generators project, because it is still pretty cool. Thank you.
I would have to measure to sustain my claim. I think that it’s faster than packer but you are right, it’s pretty much a packaged version of amazon-image.nix.
Building AMIs is even simpler (and faster) with nixos-generators. The only remaining bit is to push them to a S3 bucket and get them registered on AWS.
Neat, I was looking at https://github.com/Robertof/nixos-docker-sd-image-builder for building some sd card images for an rpi 4 spiel. And to look at getting a build for a nano pi m4 v2 going too.
Will give this a go over the weekend thanks!
Interesting project. How can it be simpler and faster if it’s calling the same
amazon-image.nixmodule that nixpkgs provides? If I needed a single nix configuration upstream of several images (EC2, Azure, GCP, etc.) then it’s definitely worth considering. Otherwise, I think usingpackerto build atop the NixOS AMI is faster because you’re not making a disk image, then sending it to S3, then waiting for VM Import.I will probably edit in a link to the
nixos-generatorsproject, because it is still pretty cool. Thank you.I would have to measure to sustain my claim. I think that it’s faster than
packerbut you are right, it’s pretty much a packaged version ofamazon-image.nix.I am having DNS troubles.DNS has been fixed.