4 ms·
> "Tags", "registries", "base images", "extraCommands"... no thanks Usually you wouldn't use any of that, unless you have some external organizational reason t
by 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 agoHaving 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!)