Comment

PhilipTheBucket@ponder.cat ⁨5⁩ ⁨days⁩ ago

I mean if it makes you happy, I won’t tell you to do anything different. I think a certain amount of it is just prejudice against Docker on my part. Just in my experience NixOS is the best of both worlds: You can have a single coherent system if everything in that system can play nice with each other, and if not, then things can be containerized completely that way still works too. And then on top it has a couple of other nice features like rolling back configs easily, or source builds that get slotted in in-place as if they were standard packages (which is generally where I abandon Docker installs of things, because making changes to the source seems like it’s going to be a big hassle).

I’m not trying to evangelize though, you should in all seriousness just do what you find to be effective.

source

Sort:hotnew top

Boomkop3@reddthat.com ⁨5⁩ ⁨days⁩ ago
Hold up, nix added containerization? How did I miss that? I will have another look now!

Also, you’re right. For small quick scripts docker can be a hassle. Nowadays though I add building a docker image as part of my project’s build/compilation process. The main reason I do this is so that I can work with whatever machine I happen to be on, then just copy paste the app to whatever machine I want it on. No extra config or even a look at the environment required. Just install docker and forget about the rest

source
- PhilipTheBucket@ponder.cat ⁨4⁩ ⁨days⁩ ago
  Hold up, nix added containerization? How did I miss that? I will have another look now!
  
  Nix is containerization.
  
  [hap@glimmer:/proc/69235/fd]$ python --version Python 3.12.8 [hap@glimmer:/proc/69235/fd]$ nix-shell -p python39 this path will be fetched (27.46 MiB download, 80.28 MiB unpacked): /nix/store/jrq27pp6plnpx0iyvr04f4apghwc57sz-python3-3.9.21 copying path '/nix/store/jrq27pp6plnpx0iyvr04f4apghwc57sz-python3-3.9.21' from 'https://cache.nixos.org/'... [nix-shell:~]$ python --version Python 3.9.21 [nix-shell:~]$ exit exit [hap@glimmer:/proc/69235/fd]$ python --version Python 3.12.8
  
  The whole “system” you get when moving from Nix to NixOS is basically just a composition of a whole bunch of those individual things, in one big container that is “the system.” But you can also fire up temporary containers trivially for particular things. I have a couple of tools with source in ~/src which, whenever I change the source, nix-os rebuild will automatically fire up a little container to rebuild them in, and if it works, it’ll deploy the completed product into my main system image for me, but if it doesn’t then nothing will have changed (and either way it throws away the container it used to attempt the build in).
  
  Each config change spawns a new container for the main system OS image (“generation”), but you can roll back to one of the earlier generations (which are, from a functional perspective, still around) if you want or if you broke something.
  
  And so on. It’s very nice.
  
  source
  - Boomkop3@reddthat.com ⁨4⁩ ⁨days⁩ ago
    Aw, meh. From what I saw it’s more like a jail, there’s no imaging the containers
    
    source
    PhilipTheBucket@ponder.cat ⁨3⁩ ⁨days⁩ ago
    Yes because that is a wrong and clunky way to do it lol.
    
    If you really wanted to, you could use dockerTools.BuildImage to create an “imaged” version of the container you made, or you could send around the flake.nix and flake.lock files exactly as someone would send around Dockerfiles. That stuff is usually just not necessary though, because it’s replaced with just a better approach (for the average-end-user case where you don’t need large numbers of Docker containers that you can deploy quickly at scale) that accomplishes the same thing.
    
    I feel like I’m not going to convince you of this though. Have fun with Docker, I guess.
    
    source
    -> View More Comments