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:
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.
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:
<channel>/<subdir>/<package name>
<version>-<build_string>
For each name+label combo, we have the following manifest of layers:
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 theinfo/index.json
file, respectively.This should be standardized in a CEP.