https://www.space.com/spacex-stacks-starship-second-test-flight-photos
'Starship is ready to launch, awaiting FAA license approval,' Elon Musk said.
Hi all. Just learned about NixOS a few weeks ago. I'm in the process of migrating several of my docker services to a new server that will have proxmox installed as the host and then a VM for docker.
I'm currently using alpine as the VM and it works well but one of the main goals of the migration is to use infrastructure as code as much as possible. All my docker services are docker compose files checked into a git repo that gets deployed. When I need to make a change, I update the git repo and pull down the latest docker compose.
I currently have a bunch of steps that I need to do on the alpine VM to make it ready for docker (qemu agent, NFS shares, etc).
NixOS promises to be able to do all that with a single config file and then create a immutable OS that never changes after that. That seems to follow the philosophy well for infrastructure as code and easy reproducibility.
Has anyone else tried NixOS as a docker host? Any issues you've encountered?
I'm just starting to upgrade my basic unraid docker to an InfraAsCode setup.
I will use unraid as Nas only. My media and backups will be on unraid, everything else on a separate proxmox VM that is running and SSD storage array for ZFS. Both the unraid and proxmox hosts share their storage via NFS. Each docker container mounts the NFS volumes as needed.
For the containers I use an alpine VM with docker. I use portainer to connect to a gitea repo (on unraid) to pull down the docker compose file.
So my workflow is, use VS code on my PC to write the compose file, commit to git, then on portainer I hit the redeploy button and it pulls the latest compose file automatically.
What's your setup?
@Lem453
@lemmy.ca