3 ms·

Standardisation at the format level will help with portability across different platform implementations.

• wmf 11y ago
  This "standardization" is pretty kludgey if you have to docker pull then docker export.
  • alex1 11y ago
    I think that's because OCI currently only has a specification for the runtime, not the distributable image. But it seems like as of a few weeks ago, work is underway to standardize the distributable image as well: https://github.com/opencontainers/image-spec https://github.com/opencontainers/image-spec
    • kalmar 11y ago
      I was almost excited! From the FAQ on the project you linked [0]: > Q: Why doesn't this project mention distribution? > A: Distribution, for example using HTTP as both Docker v2.2 and AppC do today, is currently out of scope on the OCI Scope Table. There has been some discussion on the TOB mailing list to make distribution an optional layer but this topic is a work in progress. I really hope CoreOS manage to get distribution into the scope for OCI. We need to move beyond Docker images. Standardizing on-disk layout in OCI is only mildly useful in my opinion. [0] https://github.com/opencontainers/image-spec#faq https://github.com/opencontainers/image-spec#faq
  • ibotty 11y ago
    There are other tools that can get data from a docker v2 registry.
• jamescun 11y ago
  It is standardisation of the file describing what parameters were used to build a container, ultimately every "implementation" has been a tarball of a linux filesystem which is usable with any linux container system (and possibly soon Windows).