David Arnold

@gustavovalverde Is right insofar, that a table ownership softly enforced client side especially when you have many tables will help the waiters be more productive and focused on their orders......

The idea would be that really a layer _is_ a nix store path and that OCI compliant runtimes would know how to fetch layers from nix stores. But you are...

Connecting the breadcrumbs: https://github.com/opencontainers/image-spec/issues/922

This pigen-holing result nicely illustrates the problem: ```console layers.json> INFO[0000] Excluding path /nix/store/262ksdbkjjaqnlnkl99fk1mj8rnnki1h-config.json from layer layers.json> INFO[0000] Adding 1 paths to layer (size:1638912 digest:sha256:b7a4dcedd0c8d79e869bf93cd6e9cc6149bb44afbed77fd75fd9ffc7e58d2297) layers.json> INFO[0000] Adding 1 paths to...

The corresponding popularity of the above pigeon-holing result: ``` layers.json> Score: 83102053 - /nix/store/8ckxc8biqqfdwyhr0w70jgrcb4h7a4y5-libunistring-0.9.10 layers.json> Score: 83102052 - /nix/store/w2id1hwv4vv7hvp4slgsyrydrjbfqdxc-libidn2-2.3.2 layers.json> Score: 83102051 - /nix/store/4s21k8k7p1mfik0b33r2spq5hq7774k1-glibc-2.33-108 layers.json> Score: 36403616 - /nix/store/pxqpg0iry37wgvwwfyabdv1ylr1z6i2j-color-name-1.1.3 layers.json>...

In the case that we can get a handle on the original source package (excluding container runtime environment like for example required by the entry point), then the volatility is...

After running for a while with a high `maxLayer` parameter, I realize that there is another aspect that slows the overall round-trip time down quite a lot: size-tradeoff. It _may_...

> How could we expose the nix2container attribute set? The flake output schema is by no way binding. An extreme suggestion would be `self // nix2container`. 😄

Maybe the best of both worlds would be if `contents` would symlink or hardlink the nix store paths, so that an executable can be addressed in both ways?

More context: https://github.com/input-output-hk/bitte-cells/commit/5197fa8d8ee0b4b3b41936dcab0a484dfa2fbe29 The fully qualified invocation is compatible with other nomad drivers as it preserves the **string context.** The string-only invocation is not interoperable.