4 ms·

Maybe once you learn what OCI is, you'll rethink that ;)

• otabdeveloper4 2y ago
  I know full well what OCI is. (Hint: it's a transparent attempt to be a NOT-docker and avoid infringing on whatever Docker Inc.'s latest monetization scheme is.) Using this for what Nix is doing is absolute madness. Docker is madness in general, but dragging it into Nix's core is madness cubed.
  • gcr 2y ago
    "why yes, the open-source Apache-licensed implementation controlled by the linux foundation is just as commercial as the commercial thing! i'm so contrary and interesting!" if you don't want docker-contributed code, here are some alternative implementations of the spec: https://github.com/opencontainers/runtime-spec/blob/main/implementations.md https://github.com/opencontainers/runtime-spec/blob/main/imp... I believe nix could use one of these with some volunteer effort? Perhaps you could even be the one to purge the Docker heresy from the project!
    • gcr 2y ago
      (...in hindsight, i'm sorry for posting this, it's needlessly adversarial and picky. i was mad at something unrelated this morning and i shouldn't have taken that out on you.)
    • otabdeveloper4 2y ago
      OCI is not an attempt for a useful, general-purpose, open containerization standard. It is an attempt at an open-source "just good enough" Docker clone. You understand the difference?
  • kmacleod 2y ago
    Would this be the equivalent of Mock (Fedora) or sbuild (Debian) pristine chroot builders? Containers are just fancy chroots.