It would be nice to do our part in reducing everyone's dependence on docker, in favor of tools like rkt and so on. I'm wondering if anyone would be opposed to renaming dockerTools
to containerTools
(possibly with an alias) and then iteratively adding support for e.g., rkt's ACI format. It seems like there's a lot of potential shared code between the different ecosystems, and the main thing that differs is the output format and a few smaller details.
cc @lethalman
Sure agreed. But for the design I wouldn't suggest a common front API. I'm pretty sure it will be more headaches than anything. Rather have dockerTools, rktTools that use some common shared nix code.
Fair enough!
On Mon, Nov 7, 2016 at 19:06 Luca Bruno [email protected] wrote:
Sure agreed. But for the design I wouldn't suggest a common front API. I'm
pretty sure it will be more headaches than anything. Rather have
dockerTools, rktTools that use some common shared nix code.—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/NixOS/nixpkgs/issues/20238#issuecomment-259004454,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAKP4mq38-qYnDzRS6VmbEQQWg0l0dKks5q770EgaJpZM4Krgs-
.
There is the container workgroup now, rkt has been deprecated in favor of OCI
images, docker supports OCI
images as well.
The next step would be to convert dockerTools
to produce OCI
images.
Most helpful comment
There is the container workgroup now, rkt has been deprecated in favor of
OCI
images, docker supportsOCI
images as well.The next step would be to convert
dockerTools
to produceOCI
images.