Earlier this month I mentioned on Mastodon that I was replacing a Docker-based local development environment at my day job with a Nix-based one, orchestrated with overmind and a justfile.
There was quite a lot of interest in particular in how overmind and just could be used to replace a container / compose-based local development.
While I can’t share the details of the significantly more complex migration I did at my day job (yet!
Some folks on the internet were interested in how I had managed to ditch Docker for local development. This is a slightly overdue write up on how I typically do things now with Nix, Overmind and Just.
I’m anti everything that requires daily use of arcane command line bullshit. I thought we were on the way to being over that when Windows 3.1 came out.
If it needs to be done more than once, make it a button on a little program. I’ve rolled my own for any of them that can be triggered from the windows command line. But Docker and others that require their own unique command line I can’t do that. I wouldn’t be as annoyed by Docker if Docker Desktop just did all the crap it should instead of requiring command line bullshit every damn day.
I mean… all those buttons are essentially just calling a command line in the end. And coding that button takes more work so command line is always going to be more likely to be your only option. If you find commands arcane then that’s probably an argument that the help docs should be clearer or the commands themselves should be clearer.
Making a little program that opens a window with some buttons to pin to my taskbar is infinitely easier than digging out docs and copy pasting into a command line every time I need to do anything. Paste the command once, done. It’s like 10 lines of code, plus about 3-4 for each command I add. Maybe drag the window a bit bigger when I add the button.
@astral_avocado@LGUG2Z That definitely would’ve been helpful for readers new to the Nix scene, but I don’t think that’s the purpose of this article. It’s written as more of an example of a way to move to Nix, rather than an opinion piece on why you should move away from Docker.
I won’t try to argue why you should switch. However, I would recommend you look into the subject more, Docker is a great tool, but Nix is on a diffeeent level 🙃
First I’d like to clarify that I’m not “anti-container/Docker”. 😅
There is a lot of discussion on this article (with my comments!) going on over at Tildes. I don’t wanna copy-paste everything from there, but I’ll share the first main response I gave to someone who had very similar feedback to kick-start some discussion on those points here as well:
Some high level points on the “why”:
Reproducibility: Docker builds are not reproducible, and especially in a company with more than a handful of developers, it’s nice not to have to worry about a docker build command in the on-boarding docs failing inexplicably (from the POV of the regular joe developer) from one day to the next
Cost: Docker licenses for most companies now cost $9/user/month (minimum of 5 seats required) - this is very steep for something that doesn’t guarantee reproducibility and has poor performance to boot (see below)
Performance: Docker performance on macOS (and Windows), especially storage mount performance remains poor; this is even more acutely felt when working with languages like Node where the dependencies are file-count heavy. Sure, you could just issue everyone Linux laptops, but these days hiring is hard enough without shooting yourself in the foot by not providing a recent MBP to new devs by default
I think it’s also worth drawing a line between containers as a local development tool and containers as a deployment artifact, as the above points don’t really apply to the latter.
If your dev documentation includes your devs running docker build, you’re doing docker wrong.
The whole point is that you can build a working container image and then ship it to a registry (including private registries) so that your other developers/users/etc don’t have to build them and can just run the existing image.
Then for development, you simply use a bind mount to ensure your local copy of the code is available in the container instead of the copy the container was built with.
That doesn’t solve the performance issues on Windows and Mac, but it does prevent the “my environment is broke” issues that docker is designed to solve
The whole point is that you can build a working container image and then ship it to a registry (including private registries) so that your other developers/users/etc don’t have to build them and can just run the existing image.
Agreed, we still do this in the areas where we use Docker at day job.
I think the mileage with this approach can vary depending on the languages in use and the velocity of feature iteration (ie. if the company is still tweaking product-market fit, pivoting to a new vertical, etc.).
I’ve lost count of the number of times where a team decides they need to npm install something with a heavy node-gyp step to build native modules which require yet another obscure system dependency that is not in the base layer. 😅
For this reason, we’re slowly integrating WSL2 usage onto the dev windows machines. I’m not saying that this refutes your last point, but it’s another thing to consider. This has, however, resulted in me learning to architect pretty gonzo level bash scripts when I’m accustomed to… more formal development. Lol.
Yep. That’s my personal open source project setup. I love nixos. It’s everything I like about dockerfile and a daily driver all rolled into one.
Tall ask for the workplace with a bunch of windows only folks, though, unfortunately.
Edit: I just realized you said nixos on WSL2. My bad. That’s freaking awesome, and that window manager is slick. Nice digs.
I have to have to parity with our deployments in DevOps, where debian is preferred. It’s not the worst. But I think I’m going to make a separate distro for my own personal Linux work, like you did.
I had to use Windows since I do research and development on our development team architecture. Gotta have parity there too. But that doesn’t mean I can’t cheat a bit like you, lol.
You might be interested in this article that compares nix and docker. It explains why docker builds are not considered reproducible:
For example, a Dockerfile will run something like apt-get-update as one of the first steps. Resources are accessible over the network at build time, and these resources can change between docker build commands. There is no notion of immutability when it comes to source.
and why nix builds are reproducible a lot of the time:
Builds can be fully reproducible. Resources are only available over the network if a checksum is provided to identify what the resource is. All of a package’s build time dependencies can be captured through a Nix expression, so the same steps and inputs (down to libc, gcc, etc.) can be repeated.
Containerization has other advantages though (security) and you can actually use nix’s reproducible builds in combination with (docker) containers.
Are you saying that nix will cache all the dependencies within itself/its “container,” or whatever its container replacement would be called?
Yep, sort of.
It saves each version of your dependencies to the /nix/store folder with a checksum prefixing the program name. For example you might have the following Firefox programs
Because of this you can largely avoid dependency conflicts. For example a program A could depend on /nix/store/cm1bdi4hp8g8ic5jxqjhzmm7gl3a6c46-firefox-108.0.1 and a program B could depend on /nix/store/rfr0n62z21ymi0ljj04qw2d7fgy2ckrq-firefox-114.0.1 and both programs would work as both have dependencies satisfied. AFAIK using other build systems you would have to break program A or program B (or find versions of program A and program B where both dependencies are satisfied).
That seems like an argument for maintaining a frozen repo of packages, not against containers. You can only have a truly fully-reproducible build environment if you setup your toolchain to keep copies of every piece of external software so that you can do hermetic builds.
I think this is a misguided way to workaround proper toolchain setup. Nix is pretty cool though.
That seems like an argument for maintaining a frozen repo of packages, not against containers.
I am not arguing against containers, I am arguing that nix is more reproducible. Containers can be used with nix and are useful in other ways.
an argument for maintaining a frozen repo of packages
This is essentially what nix does. In addition it verifies that the packages are identical to the packages specified in your flake.nix file.
You can only have a truly fully-reproducible build environment if you setup your toolchain to keep copies of every piece of external software so that you can do hermetic builds.
This is essentially what Nix does, except Nix verifies the external software is the same with checksums. It also does hermetic builds.
Nix is indeed cool. I just see it as less practical than maintaining a toolchain for devs to use. Seems like reinventing the wheel, instead of airing-up the tires. I could well be absolutely wrong there - my experience is mainly enterprise software and not every process or tool there is used because it is the best one.
I see it as less practical mainly due to the extant tooling and age/maturity of the project.
The ways that I’m most familiar with are use of software like Artifactory - basically a multi-repo. Using such a tool, any package or artifact can be readily retained for future use. Then, for builds, one only needs to ensure that it is used as the package source, regardless of type (PyPy, Docker image, binary, RPM, etc).
Alternatively, one can use individual repos for any relevant package type but that’s a bit more overhead to manage.
@nickwitha_k@uthredii I’d like to think a better analogy would be that nix is like using a 3D model of a wheel instead of a compass and a straightedge to make wheels hehe 🙃
Cost: Docker licenses for most companies now cost $9/user/month
Are you talking about Docker Desktop and/or Docker Hub? Because plain old docker is free and open source, unless I missed something bug. Personally I’ve never had much use for Docker Desktop and I use GitLab so I have no reason to use Docker Hub.
On an individual scale and even some smaller startup scales, things are a little bit different (you qualify for the free tier, everyone you work with is able to debug off-the-beaten-path Docker errors, knowledge about fixes is quick and easy to disseminate, etc.), but the context of this article and the thread on Mastodon that spawned it was a “unicorn” company with an engineering org comprised of hundreds of developers.
My point is that Docker Desktop is entirely optional. On Linux you can run Docker Engine natively, on Windows you can run it in WSL, and on macOS you can run it in a VM with Docker Engine, or via something like hyperkit and minikube. And Docker Engine (and the CLI) is FOSS.
I understood your point, and while there are situations where it can be optional, in a context and scale of hundreds of developers, who mostly don’t have any real docker knowledge, and who work almost exclusively on macOS, let alone enough to set up and maintain alternatives to Docker Desktop, the only practical option becomes to pay the licensing fees to enable the path of least resistance.
We are over 1000 developers and use docker ce just fine. We use a self hosted repository for our images. IT is configuring new computers to use this internal docker repository by default. So new employees don’t even have to know about it to do their first docker build.
We all use Linux on our workstations and laptops. That might make it easier.
Op comes off a bit, uninformed. E.g. I use docker engine and docker compose inside WSL2 on windows and performance is fine, then I use Intellij to manage images/containers, the service tab handles the basics. If I need to do anything very involved I use the cli.
Docker is fine, the docker desktop panic really only revealed who never took the time to learn how to use docker and what the alternative UIs are.
We all use Linux on our workstations and laptops. That might make it easier.
You are living my dream!
I think this is the key piece; the experience of Docker on Linux (including WSL if it’s not hooking into Docker Desktop on Windows) and on macOS is just so wildly difference when it comes to performance, reliability and stability.
Appreciate the in-depth response! I’ve always been interested in Nix but I’m scared of change lol. And I’m a single systems administrator on a team of mostly non-technicals so large changes like that are … less necessary. Plus you know, mostly dealing with enterprise software on windows unfortunately. One of these days.
Docker is like, my favorite utility tool, for both deployment AND development (my replacement for Python virtual environments). I wanted to hear more of why I shouldn’t use it also.
Right? If it’s about ease of insight into containers for debugging and troubleshooting, I can kinda see that. Although I’m so used to working with containers it isn’t a barrier really to me anymore.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !programming@programming.dev
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person’s post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
Follow the programming.dev instance rules
Keep content related to programming in some way
If you’re posting long videos try to add in some form of tldr for those who don’t want to watch videos
I wish he had written why he’s so anti-container/docker. That’s a pretty unusual stance I haven’t been exposed to yet.
I’m anti everything that requires daily use of arcane command line bullshit. I thought we were on the way to being over that when Windows 3.1 came out.
If it needs to be done more than once, make it a button on a little program. I’ve rolled my own for any of them that can be triggered from the windows command line. But Docker and others that require their own unique command line I can’t do that. I wouldn’t be as annoyed by Docker if Docker Desktop just did all the crap it should instead of requiring command line bullshit every damn day.
I mean… all those buttons are essentially just calling a command line in the end. And coding that button takes more work so command line is always going to be more likely to be your only option. If you find commands arcane then that’s probably an argument that the help docs should be clearer or the commands themselves should be clearer.
Making a little program that opens a window with some buttons to pin to my taskbar is infinitely easier than digging out docs and copy pasting into a command line every time I need to do anything. Paste the command once, done. It’s like 10 lines of code, plus about 3-4 for each command I add. Maybe drag the window a bit bigger when I add the button.
We were talking about software development and deployment in this thread, not necessarily how easy your desktop GUI is to use.
No shit. I’m saying the tools I had to make myself should come standard instead of wasting dev time on command line bullshit.
@astral_avocado @LGUG2Z That definitely would’ve been helpful for readers new to the Nix scene, but I don’t think that’s the purpose of this article. It’s written as more of an example of a way to move to Nix, rather than an opinion piece on why you should move away from Docker.
I won’t try to argue why you should switch. However, I would recommend you look into the subject more, Docker is a great tool, but Nix is on a diffeeent level 🙃
Hi!
First I’d like to clarify that I’m not “anti-container/Docker”. 😅
There is a lot of discussion on this article (with my comments!) going on over at Tildes. I don’t wanna copy-paste everything from there, but I’ll share the first main response I gave to someone who had very similar feedback to kick-start some discussion on those points here as well:
Some high level points on the “why”:
Reproducibility: Docker builds are not reproducible, and especially in a company with more than a handful of developers, it’s nice not to have to worry about a
docker buildcommand in the on-boarding docs failing inexplicably (from the POV of the regular joe developer) from one day to the nextCost: Docker licenses for most companies now cost $9/user/month (minimum of 5 seats required) - this is very steep for something that doesn’t guarantee reproducibility and has poor performance to boot (see below)
Performance: Docker performance on macOS (and Windows), especially storage mount performance remains poor; this is even more acutely felt when working with languages like Node where the dependencies are file-count heavy. Sure, you could just issue everyone Linux laptops, but these days hiring is hard enough without shooting yourself in the foot by not providing a recent MBP to new devs by default
I think it’s also worth drawing a line between containers as a local development tool and containers as a deployment artifact, as the above points don’t really apply to the latter.
If your dev documentation includes your devs running
docker build, you’re doing docker wrong.The whole point is that you can build a working container image and then ship it to a registry (including private registries) so that your other developers/users/etc don’t have to build them and can just run the existing image.
Then for development, you simply use a bind mount to ensure your local copy of the code is available in the container instead of the copy the container was built with.
That doesn’t solve the performance issues on Windows and Mac, but it does prevent the “my environment is broke” issues that docker is designed to solve
Agreed, we still do this in the areas where we use Docker at day job.
I think the mileage with this approach can vary depending on the languages in use and the velocity of feature iteration (ie. if the company is still tweaking product-market fit, pivoting to a new vertical, etc.).
I’ve lost count of the number of times where a team decides they need to
npm installsomething with a heavynode-gypstep to build native modules which require yet another obscure system dependency that is not in the base layer. 😅For this reason, we’re slowly integrating WSL2 usage onto the dev windows machines. I’m not saying that this refutes your last point, but it’s another thing to consider. This has, however, resulted in me learning to architect pretty gonzo level bash scripts when I’m accustomed to… more formal development. Lol.
NixOS on WSL2 is actually my development environment of choice these days! (With my tiling window manager komorebi, of course! 😀)
I’ve been looking for a tiling vm for windows but haven’t come across komorebi, thanks for mentioning it!
Yep. That’s my personal open source project setup. I love nixos. It’s everything I like about dockerfile and a daily driver all rolled into one.
Tall ask for the workplace with a bunch of windows only folks, though, unfortunately.
Edit: I just realized you said nixos on WSL2. My bad. That’s freaking awesome, and that window manager is slick. Nice digs.
I have to have to parity with our deployments in DevOps, where debian is preferred. It’s not the worst. But I think I’m going to make a separate distro for my own personal Linux work, like you did.
I had to use Windows since I do research and development on our development team architecture. Gotta have parity there too. But that doesn’t mean I can’t cheat a bit like you, lol.
What makes you say that?
My team relies on Docker because it is reproducible…
Highly recommended viewing if you’d like to learn more about the limits of reproducibility in the Docker ecosystem.
Here is an alternative Piped link(s): https://piped.video/watch?v=pfIDYQ36X0k
Piped is a privacy-respecting open-source alternative frontend to YouTube.
I’m open-source, check me out at GitHub.
I’m going to give it a watch. Thanks for sharing!
You might be interested in this article that compares nix and docker. It explains why docker builds are not considered reproducible:
and why nix builds are reproducible a lot of the time:
Containerization has other advantages though (security) and you can actually use nix’s reproducible builds in combination with (docker) containers.
I’ll certainly give this a read!
Are you saying that nix will cache all the dependencies within itself/its “container,” or whatever its container replacement would be called?
Yep, sort of.
It saves each version of your dependencies to the /nix/store folder with a checksum prefixing the program name. For example you might have the following Firefox programs
Because of this you can largely avoid dependency conflicts. For example a program A could depend on
/nix/store/cm1bdi4hp8g8ic5jxqjhzmm7gl3a6c46-firefox-108.0.1and a program B could depend on/nix/store/rfr0n62z21ymi0ljj04qw2d7fgy2ckrq-firefox-114.0.1and both programs would work as both have dependencies satisfied. AFAIK using other build systems you would have to break program A or program B (or find versions of program A and program B where both dependencies are satisfied).That seems like an argument for maintaining a frozen repo of packages, not against containers. You can only have a truly fully-reproducible build environment if you setup your toolchain to keep copies of every piece of external software so that you can do hermetic builds.
I think this is a misguided way to workaround proper toolchain setup. Nix is pretty cool though.
I am not arguing against containers, I am arguing that nix is more reproducible. Containers can be used with nix and are useful in other ways.
This is essentially what nix does. In addition it verifies that the packages are identical to the packages specified in your flake.nix file.
This is essentially what Nix does, except Nix verifies the external software is the same with checksums. It also does hermetic builds.
Nix is indeed cool. I just see it as less practical than maintaining a toolchain for devs to use. Seems like reinventing the wheel, instead of airing-up the tires. I could well be absolutely wrong there - my experience is mainly enterprise software and not every process or tool there is used because it is the best one.
There are definately some things preventing Nix adoption. What are the reasons you see it as less practical than the alternatives?
What are alternative ways of maintaining a toolchain that achieves the same thing?
I see it as less practical mainly due to the extant tooling and age/maturity of the project.
The ways that I’m most familiar with are use of software like Artifactory - basically a multi-repo. Using such a tool, any package or artifact can be readily retained for future use. Then, for builds, one only needs to ensure that it is used as the package source, regardless of type (PyPy, Docker image, binary, RPM, etc).
Alternatively, one can use individual repos for any relevant package type but that’s a bit more overhead to manage.
@nickwitha_k @uthredii I’d like to think a better analogy would be that nix is like using a 3D model of a wheel instead of a compass and a straightedge to make wheels hehe 🙃
I quite like the sound of Nix, every time I touch on it but haven’t really dug in yet. You’re making me really want to though.
I remember when I first got a work Macbook and was confused why I had to install some ‘Docker Desktop’ crap.
I also learnt how much Docker images care about the silicon they’re built on… Fucking M1 chip can be a pain…
Are you talking about Docker Desktop and/or Docker Hub? Because plain old docker is free and open source, unless I missed something bug. Personally I’ve never had much use for Docker Desktop and I use GitLab so I have no reason to use Docker Hub.
I believe this is the Docker Desktop license pricing.
On an individual scale and even some smaller startup scales, things are a little bit different (you qualify for the free tier, everyone you work with is able to debug off-the-beaten-path Docker errors, knowledge about fixes is quick and easy to disseminate, etc.), but the context of this article and the thread on Mastodon that spawned it was a “unicorn” company with an engineering org comprised of hundreds of developers.
My point is that Docker Desktop is entirely optional. On Linux you can run Docker Engine natively, on Windows you can run it in WSL, and on macOS you can run it in a VM with Docker Engine, or via something like hyperkit and minikube. And Docker Engine (and the CLI) is FOSS.
I understood your point, and while there are situations where it can be optional, in a context and scale of hundreds of developers, who mostly don’t have any real
dockerknowledge, and who work almost exclusively on macOS, let alone enough to set up and maintain alternatives to Docker Desktop, the only practical option becomes to pay the licensing fees to enable the path of least resistance.We are over 1000 developers and use
docker cejust fine. We use a self hosted repository for our images. IT is configuring new computers to use this internal docker repository by default. So new employees don’t even have to know about it to do their firstdocker build.We all use Linux on our workstations and laptops. That might make it easier.
Op comes off a bit, uninformed. E.g. I use docker engine and docker compose inside WSL2 on windows and performance is fine, then I use Intellij to manage images/containers, the service tab handles the basics. If I need to do anything very involved I use the cli.
Docker is fine, the docker desktop panic really only revealed who never took the time to learn how to use docker and what the alternative UIs are.
You are living my dream!
I think this is the key piece; the experience of Docker on Linux (including WSL if it’s not hooking into Docker Desktop on Windows) and on macOS is just so wildly difference when it comes to performance, reliability and stability.
Appreciate the in-depth response! I’ve always been interested in Nix but I’m scared of change lol. And I’m a single systems administrator on a team of mostly non-technicals so large changes like that are … less necessary. Plus you know, mostly dealing with enterprise software on windows unfortunately. One of these days.
Docker is like, my favorite utility tool, for both deployment AND development (my replacement for Python virtual environments). I wanted to hear more of why I shouldn’t use it also.
Right? If it’s about ease of insight into containers for debugging and troubleshooting, I can kinda see that. Although I’m so used to working with containers it isn’t a barrier really to me anymore.
yup. it’s a breeze especially for interpreted langs. mount the source code, expose the ports and voila. need a db?