Skip to main content
Version: v3.9.0

OCI registry

Goal​

Create a Registry row for ghcr.io with type: oci. The wafer-defect ONNX artifact is an OCI blob. Built-in registry 1 (docker.io) cannot pull it.

You need an Edgelet node you will call edge-c. You can change agent.name later if the node has another name.

YAML​

Use a public endpoint when the package is world-readable. Save this as ghcr-registry.yaml.

ghcr-oci
apiVersion: datasance.com/v3
kind: Registry
metadata:
  name: ghcr-oci
spec:
  url: ghcr.io
  type: oci
  private: false

For a private package, set private: true and add a robot username and password. See Registries.

Deploy​

potctl configure current-namespace <replace-me!>
✔ Successfully configured current-namespace

potctl deploy -f ghcr-registry.yaml
potctl get registries

ID  URL                     USERNAME       PRIVATE  TYPE  INSECURE  
1   docker.io                              false    oci   false     
2   from_cache                             false    oci   false     
3   https://huggingface.co                 false    hf    false     
...   
9   ghcr.io                                false    oci   false

What you should see​

A row with type: oci and url: ghcr.io. Write down the numeric id. The model page uses it as spec.registryId.

Common mistakes​

Using registry 1 on the model. That row does not serve this GHCR artifact.

Leaving out type: oci. The catalog expects an OCI layout for this model.

Next​

Wafer-defect model

Group 3See anything wrong with the document? Help us improve it!

Edit this page on GitHub!