We need a Grafana dashboard for this.
08.09.2025 06:57
👍 0
🔁 0
💬 0
📌 0
We need a Grafana dashboard for this.
Hello, London! ☕ 👋 We’re live at #KubeCon! Swing by the 2nd floor of the Platinum Suite (right by the coffee spot) and come say hi to the Flox team. We’ll be there till 4 PM today! We’d love to chat, show you what we’re building, and hear what you’re up to!
#KubeCon
Every new tool or abstraction we adopt solves one problem but creates others.
This is the story of discovering Nix. Of stepping away from the madness of layer upon layer of abstraction.
Of learning to love a deterministic approach to building software.
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 :)
Promotional picture of me with the SCaLE22x branding advertising that I’ll be giving a talk with title “Using Nix to build pretty small images” at the Cloud Native Days LA (cloudnativedays.org).
I’ll be speaking at Cloud Native Days LA in #SCaLE22x about leveraging #nix / #nixos to build pretty small container images. I’ll make an attempt at showing you the benefits of using something like Nix to do this, and daydream about possible future integrations. Looking forward to seeing you there!
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?
Flox and Containers = the Best of Both Worlds 🌍
🛠️ Develop locally with Flox for convenience
📦 Deploy Flox environments as containerized artifacts for CI and prod
🔁 Get reproducibility with determinism and ⛔ no bloat
[https://buff.ly/4hetTrW]
Some of you may know that I play in a metal band in my spare time. A year ago, we released our first EP, "Set Me Free". To celebrate, we're finally releasing our live video we made that night! I'd really appreciate it if you gave it a listen. 😁
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.