4 ms·

Um.. `dockerTools`/`ociTools`? https://nixos.org/manual/nixpkgs/stable/#chap-images https://nixos.org/manual/nixpkgs/stable/#chap-images

• chriswarbo 4y ago
  > dockerTools "Tags", "registries", "base images", "extraCommands"... no thanks > ociTools IIRC, this generates a runnable container (i.e. a directory, with accompanying config); not a container image, e.g. suitable for uploading to AWS ECS.
  • kam 4y ago
    > "Tags", "registries", "base images", "extraCommands"... no thanks All of which are optional. It's just doing the same thing as your tar commands.
    • chriswarbo 4y ago
      > All of which are optional True, but they're dangerous enough that I'd still at least want a wrapper function which doesn't accept them at all. > It's just doing the same thing as your tar commands. Not quite: I came up with those commands by reading the OCI specifications. In contrast, the output of the dockerTools functions does not quite follow those specifications, and appears to be more Docker-specific.
      • pxc 4y ago
        Nix 3 has a dead simple, builtin CLI frontend for doing this with built packages: https://nixos.org/manual/nix/unstable/command-ref/new-cli/nix3-bundle.html https://nixos.org/manual/nix/unstable/command-ref/new-cli/ni... It uses dockerTools: https://github.com/NixOS/bundlers/blob/master/flake.nix https://github.com/NixOS/bundlers/blob/master/flake.nix maybe a bundler can be added that uses OCI tools, thus providing such a wrapper and giving a nice CLI for it
  • Nullabillity 4y ago
    > "Tags", "registries", "base images", "extraCommands"... no thanks Usually you wouldn't use any of that, unless you have some external organizational reason to depend on a base image. A typical image would just be: dockerTools.streamLayeredImage { name = "mything"; config.Cmd = "${mything}/bin/mything"; }
    • chriswarbo 4y ago
      Having equivalents like ociTools.buildImage and ociTools.streamLayeredImage functions would certainly be nice; but at the moment there's only ociTools.buildContainer, which doesn't use images. I'll see if Nixpkgs is receptive to having such functionality, as a unification of what I've done with what exists in dockerTools (although I need to check that my employer's happy for it to be upstreamed first!)