We need a Grafana dashboard for this.

Must be the water.

I see it’s turning up more and more at events like DevOpsDays. The community also organises meet-ups around the world, so you could try your luck there. There’s also and official matrix channel listed on the website. 😁

I’ll ask @tomberek.bsky.social to upload them. 😉

I have :)

One of my favourite tricks in the book. Mitchell Hashimoto has a very good blog post about this, I recommend giving that a read. mitchellh.com/writing/nix-...

I'm a bit vague on how silverblue actually does its package management. Does it support RPMs like Fedora does? If so, we do ship an RPM flox.dev/docs/install...

I'll also create a ticket to look into the excessive layer count. Looking into it with dive myself, there are a few things in there which I think we can safely remove already.

Okay, then I get the comment. I'll admit that the container is quite sizable, and there are probably a few paths in there that we could shave off that aren't contributing much right now. But it should provide you with a fairly accurate environment to play around in.

Oh, wait. Are you doing a flox containerize of one of your environments, or are you docker pulling one of our images?

This is because we use nixpkgs' dockerTools.steamLayeredImage function under the hood. This puts every single dependency of your environment into its own image layer. Now, we could expose an option to tell the function the max layers it's allowed to use.

Out of curiosity, why is this surprising?

I call it ancient software, is that okay?

Been doing the git commit --allow-empty-message myself. Talk is cheap, show me the code. 😁

You forgot Git. 😁

Meant to type DevOps, got autocorrect to DevOpsDays, sorry. 🙃

Oh, there’s also this pretty recent post which might be of interest to you. medium.com/@pierre_4965...

Here are some of my favourite resources.

mitchellh.com/writing/nix-...
nix.dev/index.html
flox.dev/blog/making-...

When it comes to DevOpsDays specifically, I’ve used it to provide all the tools necessary to bootstrap and maintain infrastructure. As well as tried using it as a container generator. The process is quite nice once you get over the language. At @flox.dev we’re also trying to make this easier still.