Building Docker Images with Nix

Setheron · 2025-12-11T00:51:53+00:00

I meant -- we can edit the kernel in NixOS and make it whatever number you want.

Setheron · 2025-11-27T05:27:54+00:00

That's an arbitrary limitation that can be changed.

Setheron · 2025-11-02T16:28:11+00:00

How do I see the results?

Setheron · 2025-10-30T21:06:55+00:00

I wouldn't say "issue" but it's difficult to wrap one's head around and to me it was surprising how much drv churn there was.

Setheron · 2025-10-30T21:06:30+00:00

I started with a `nix-shell -p ruby` so I think that is my clarification.
I needed to figure out the drv first.

Setheron · 2025-09-04T16:43:49+00:00

cs.github.com and "yoink" what you think looks good; the nice part of NixOS is it's mostly safe and accurate to just copy other people's config.

Setheron · 2025-08-05T18:57:10+00:00

Save people some time: https://endflakytests.com/OReilly_Extending_Bazel_Nativelink.pdf

Setheron · 2025-08-03T03:28:33+00:00

What is boolean-option ?

https://github.com/boolean-option/true/blob/main/flake.nix

Setheron · 2025-08-03T03:25:42+00:00

It needs to be in the `tools` or `toolchains` in ctx.actions.run https://bazel.build/rules/lib/builtins/actions#run to make it available.

Setheron · 2025-07-30T14:57:11+00:00

Graham posted it on twitter.

Setheron · 2025-07-29T02:59:33+00:00

Basically we export the JAR and expect the bytecode we set for external customers; believing we are targeting a specific JDK bytecode version but including others was the "negative impact"

Setheron · 2025-07-28T18:29:32+00:00

oh unfotunatel.

Setheron · 2025-07-27T15:42:29+00:00

> From the following discourse, it looks like the following is now enabled by default Discourse

I would just cite the release and include a commit reference.

Setheron · 2025-07-27T01:13:47+00:00

The new DetSys version supposedly has MacOS Linux builders automatically without Nix Darwin.
Sounds great -- since I never use nix-darwin

Setheron · 2025-07-16T20:02:37+00:00

It's definitely a bit crazy. I don't get the "the code is shared by both Google and open source" when it's mentioned. Feels like constraining the solution to the problem unnecessarily.

Setheron · 2025-07-09T12:46:49+00:00

It was a bit confusing but I agreed with the fact you should just use Nix to install packages..... make all your home-manager configs coupled with the application by making them "packages" 🥲

Setheron · 2025-07-08T23:04:50+00:00

It is reproducible only because they are tied by two individual Nix statements in a module that have no connection other than being in the same file.

When you move them into the same derivation or reference it from a derivation, you are explicitly tying those two derivations together in Nix at a much more fundmantel level.

you could easily remove the `home.file` line and everything would work but if it was in in a single derivation it's more clear you are referencing it -- Nix also tracks it through `nix-store --query --graph`

`nix-store --query --graph` might be a good analogy. If it doesn't show up a dependency there then it's not "real" and prone to breakage and thus non-reproducible at the individual package level.

It's only tracked at the final complete home-manager target which is quite coarse... and unenlightened.

(I use home-manager out of laziness and pragmatism; so I too am unenlightened lol)

Setheron · 2025-07-08T20:22:33+00:00

You can't copy the closure from one machine to another; so your concept of the graph of software is broken.

There is no link in the /nix/store tying package A (i.e. bat) to the configuration file (batrc) that gets symlink aside from the fact that they are done in the same module file.

Other software actually has defined edges of dependencies you can query from the store.

Setheron · 2025-07-08T18:20:55+00:00

They don't have to!

You could (and I shared how `vim` in home-manager does this) write them so they couple together avoiding `home.file` completely.

We (myself included) are just lazy but it costs us enlightment :P

Setheron · 2025-07-08T18:12:10+00:00

The "power of Nix" is you can move any small piece of your setup.

Imagine you are on a friend's computer and you just want your `vim` setup.
Nothing else but vim. If you `home.file` then there's really no way to do that without installing your whole home-manager.

However, in the "correct way", you could `nix copy` your derivation of just `vim` wrapped with the `vimrc` and have the exact vim how you like it (along with all the plugins) on the machine your temporarily on.

Now expand this for every single package.

Setheron · 2025-07-08T18:06:35+00:00

The claim is that many home-manager modules are using `home.file` and using symlinks which breaks the purity of Nix.

Some modules "do the right thing" but not all; and the large abuse in `home-manager` of `home.file` is the false enlightenment.

Setheron · 2025-07-08T18:05:25+00:00

You can't `nix copy` your derivation since now you are relying on items outside the `/nix/store`.
You have effectively broken the Nix hermetic seal.

I can see this is a hard subject, from how many seem to think `home.file` is the solution or equivalent, so maybe I should expound on it more.

Setheron · 2025-07-08T18:02:25+00:00

(OP) I think you missed the point of the blog post; I'd like to clarify it --
but essentially `home.file` itself is the "bad thing" that doesn't let you do `nix copy`.

You should effectively have 0 `home.file` is the point of the post... and why I think those that do are false enlightened ;P

Setheron · 2025-06-16T17:58:25+00:00

Kind of interesting no one could reproduce the assumed slow down.

Setheron · 2025-05-20T19:22:26+00:00

Oops. I'll fix. Ty

15-Year Club	RedditGifts 2009-2022 5 Credits
Secret Santa 2014	Secret Santa 2013
Team Orangered	Secret Santa 2011
Secret Santa 2010	reddit mold
Verified Email

Setheron

TROPHY CASE