Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CEP request: OCI packaging #69

Open
jaimergp opened this issue Apr 12, 2024 · 0 comments · May be fixed by #70
Open

CEP request: OCI packaging #69

jaimergp opened this issue Apr 12, 2024 · 0 comments · May be fixed by #70

Comments

@jaimergp
Copy link
Contributor

https://github.com/orgs/channel-mirrors/packages has a mostly complete mirror of conda-forge and bioconda in GHCR.io. Each anaconda.org artifact (be it tar.bz2 .conda), has been pushed there under the following conventions:

  • Name of the "container": <channel>/<subdir>/<package name>
  • Label of the container: <version>-<build_string>

For each name+label combo, we have the following manifest of layers:

{
  "digest": "sha256:<hash>",
  "mediaType": "application/vnd.oci.image.manifest.v1+json",
  "size": <size in bytes>,
  "config": {
    "digest": "sha256:<hash>",
    "mediaType": "application/vnd.unknown.config.v1+json",
    "size": <size in bytes>
  },
  "layers": [
    {
      "digest": "sha256:<hash>",
      "mediaType": "application/vnd.oci.image.layer.v1.tar",
      "size": <size in bytes>
    },
    {
      "digest": "sha256:<hash>",
      "mediaType": "application/vnd.conda.package.v2",
      "size": <size in bytes>
    },
    {
      "digest": "sha256:<hash>",
      "mediaType": "application/vnd.conda.info.v1.tar+gzip",
      "size": <size in bytes>
    },
    {
      "digest": "sha256:<hash>",
      "mediaType": "application/vnd.conda.info.index.v1+json",
      "size": <size in bytes>
    }
  ]
}

I think the tar and conda layers correspond to tar.bz2 and .conda ones. Always present, but only one is populated. The info layers correspond to the compressed info/ contents and the info/index.json file, respectively.

This should be standardized in a CEP.

@jaimergp jaimergp linked a pull request Apr 15, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant