| 4 Feb 2026 |
 crop | * hm i want to try to build this: https://github.com/daisy-embassy/daisy-embassy/blob/master/rust-toolchain is it correct when i think that fenix only provide the toolchain for rust-std?
typos 😭 | 19:48:55 |
| 6 Feb 2026 |
|  Haradion changed their display name from blm768 to Haradion. | 21:21:29 |
| 7 Feb 2026 |
 denommus | I'm trying to build a docker image with dockerTools.buildImage, but it becomes huge (2 GB, when a pure docker file is just around 45 MB). I'm using naersk to build the binary itself. Is there a way naersk doesn't include all the junk that it's including, or should I use another build tool? | 00:43:01 |
 Gaétan Lepage | You might want to check out nix-snapshotter | 09:24:07 |
 Ben Sparks | Or nix2container | 10:46:01 |
|  Šimon Brandner joined the room. | 14:06:38 |
|  @simon.brandner:envs.net left the room. | 15:41:17 |
| Šimon Brandner set a profile picture. | 16:40:42 |
| denommus | naersk was indeed to blame, the path-info of a naersk package includes everything used by the build. I used crate2nix and it was much smaller. But... crate2nix has some sort of bug where I can't use rust-overlay nor fenix | 17:14:28 |
| denommus | I will now try crane | 17:15:38 |
| denommus | crane also has a smaller path-info | 17:48:28 |
| denommus | yeah, crane produced a smaller image. It could be even smaller, but crane produces a single derivation out of the entire workspace, while crate2nix generates one derivation per crate. So I can have an image per crate in crate2nix's case. While in crane each image will have all the binaries of the crates | 18:20:42 |
| denommus | so I guess I'll open an issue for crate2nix to fix the issue with fenix and rust-overlay | 18:21:03 |
| Ben Sparks | The only thing that changed recently is that IFD imports can now choose their rust and cargo versions:
https://github.com/nix-community/crate2nix/pull/390
Does following this approach change with crate2nix for you? | 18:30:19 |
| Ben Sparks | * The thing that would influence this, that changed recently, is that IFD imports can now choose their rust and cargo versions:
https://github.com/nix-community/crate2nix/pull/390
Does following this approach change with crate2nix for you? | 18:30:40 |
| 9 Feb 2026 |
|  novedevo changed their display name from Devon to novedevo. | 18:42:35 |
| novedevo set a profile picture. | 18:43:58 |
|  amadaluzia removed their profile picture. | 22:31:11 |
| amadaluzia set a profile picture. | 22:32:21 |
| 10 Feb 2026 |
|  pneumatic changed their display name from ribosomerocker to pneumatic. | 10:28:50 |
| denommus | I'm not using IFD | 11:29:08 |
| denommus | as promised, I opened an issue: https://github.com/nix-community/crate2nix/issues/436 | 11:29:31 |
| denommus | hm, it works with IFD | 11:39:27 |
|  ret2pop changed their display name from ret2pop ⚡️ to ret2pop. | 22:01:38 |
| 11 Feb 2026 |
| denommus | I think I'll try with IFD, but I still need help with one thing: how do I make the flake read the .sqlx files? I couldn't find this information on Google | 12:58:30 |
| Ben Sparks | Which .sqlx files are you talking about? Why should your flake have to read them?= | 13:27:31 |
| Ben Sparks | * Which .sqlx files are you talking about? Why should your flake have to read them? | 13:27:33 |
| denommus | they're generated by cargo sqlx prepare, and are used to validate my queries without a db connection. In theory having those files is perfect for pure builds with sqlx macros | 13:28:42 |
| Ben Sparks | can they not be added to the repository? or are they unwieldy build artifacts | 13:30:34 |
| denommus | that's the thing, they are in the repo, but for some reason crate2nix is not seeing them | 13:35:16 |
