tomberek

Recommend replacing this `--closure-size` with `--size` and obtaining the closure size somewhere else; preferably using the local store where this would run over the SQL instead of network. And only...

The layers are re-used. You see them reloaded in the streaming load because they load them in, but you'll notice that the layer hashes are the same. The outermost manifest...

Upstream PR is merged... waiting for it to be available in flox/nixpkgs, and then we can do a bump

@flox/cli When do we plan to do a lock bump? (or more precisely, to bump the bundled Nixpkgs used by pkgdb?)

okay. still need to wait for it to reach stable: https://github.com/flox/nixpkgs/tree/stable/pkgs/build-support/docker

Update: still blocked. Upstream changes have not yet made it to [stable](https://github.com/flox/nixpkgs/tree/stable/pkgs/build-support/docker) Options: 1. Use non-stable branch of flox/nixpkgs [here](https://github.com/flox/flox/blob/main/flake.nix#L23). This would revert the intention of [this commit](https://github.com/flox/flox/commit/d732cb871eab2c40585346bafe9b535fe078e04a). 2. Vendor...

> I think we need to do #2316 first I was adding that to this (only the nixpkgs, not the rest) ... but if 2316 is already on its way......

The layer hashes are stable. ``` podman image inspect localhost/flox:latest | jq '.[].RootFS.Layers[]' | head -n60 | sha256sum b019c8eb1778457215001ee312ad215820c7ff7b4f4f8e13ae48190db2ffd62b - ``` The json of the top-level manifest still records the...

Instructions to try a "containerize it from inside a flox docker container": https://github.com/flox/flox-experimental-plugins/tree/master/pkgs/flox-containerize-docker

Likely the carriage return stops the one-line comment: https://github.com/NixOS/nix/blob/master/src/libexpr/lexer.l#L284 `eol` from Megaparsec only understands `\n`. Something like this might work, but change things elsewhere? position values might get messed up?...