Boomkop3

The issue is, nix builds are only guaranteed to be reproducible if the dependencies don't change. Which they shouldn't, but you can't trust the internet to be consistent. Things won't be there to be fetched forever.

Images do. And you can turn one into a container in seconds. I suppose it's a matter of preference. I like one a package to be independent

It also adds more fodder for insurance companies to try to not do their job

Did you grow up some some sort of post modern thriller?

Aw, meh. From what I saw it's more like a jail, there's no imaging the containers

Ah, then they don't have to worry

No I threw it in a docker container

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

update: installing docker on nixos (on a vm) with a nix package failed, not sure why. Perhaps some dependencies were no longer available?

update: nix is is available as a docker image. I'm running it now, we shall see how it goes

Perhaps it's improved over the last year, I can give it a shot. But yes, for my own packaged applications without shared dependencies, docker is handy. And that's exclusively what I run

Ye that's handy, until some script inside a library or something doesn't

When I tried it it looked really cool. Up until it just.. didn't work. And then looking around I found a bunch of people giving me better snippets of scripts and it was not helpful

But given I just need docker and nothing more, I did not bother and looked further

Tried both, didn't like 'm, using docker now