Can't upload oci-image resources from any registry but Docker Hub
Metadata
Current evaluation
Registry restriction was lifted in Charmcraft 1.1 by PR #391 (commit bf2d2c5e), allowing upload-resource to use local images or images from any registry.
Resolution: closed resolved
Reason: The maintainer confirmed that the new upload-resource behavior was released in 1.1. PR #391, commit bf2d2c5e, implemented the registry-independent workflow.
Evaluated by: mr-cal-bot
No scores available.
Issue body
```
$ charmcraft upload-resource k8s-keystone-auth k8s-keystone-auth-image --image rocks.canonical.com/cdk/k8scloudprovider/k8s-keystone-auth:v1.21.0
The registry server cannot be specified as part of the image (the format is [organization/]name[:tag|@digest]). (full execution logs in /tmp/charmcraft-log-7qw9appt)
$ charmcraft version
1.0.0
```
My team has a variety of testing environments that do not have access to Docker Hub. Those environments do have access to rocks.canonical.com, though, and I would like to have the resource reference that registry instead. It seems that isn't allowed. Why?
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | Registry restriction was lifted in Charmcraft 1.1 by PR #391 (commit bf2d2c5e), allowing upload-resource to use local images or images from any registry. | |
| stealth/space-bunny-alpha | — | closed resolved | Registry restriction was lifted in Charmcraft 1.1. The new upload-resource behavior, implemented by merged PR #391 (commit bf2d2c5e), supported local images and images from any registry. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Fixed in version 1.1. Support for uploading OCI images from any registry or local builds was added, resolving the Docker Hub restriction. | |
| qwen/qwen3.6-35b-a3b | — | — | Resolved in version 1.1. The Docker Hub restriction was removed, enabling OCI image uploads from any registry or local machine. | |
| qwen/qwen3.6-35b-a3b | — | — | Resolved in charmcraft 1.1. The upload-resource command now accepts OCI images from any registry, removing the previous Docker Hub-only restriction. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Fixed in charmcraft 1.1. The Docker Hub restriction for OCI image uploads was removed, enabling pushes from local machines or any external registry. |
Update history
No update history recorded yet.
Related work
-
Likely Fixed By:
charmcraft#391
(confidence 98%)
Implemented support for local images and images from any registry.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1685 Multi-arch OCI image incorrectly uploaded to Charmhub registry | charmcraft | closed | Fixed multi-architecture resource uploads in Charmcraft 2.7 by PR #1462 (commit 566103b8), ensuring complete OCI images reach Charmhub. | |
| #839 Upload resources on charmcraft upload when specified as upstream-resource in the metadata file | charmcraft | closed | Feature request to auto-upload OCI resources during `charmcraft upload` was declined by design: maintainer refused to have Charmcraft copy Docker Hub images into Canonical's registry and cited upload inefficiency; user advised to script it using JSON output. | |
| #444 unable to upload oci-image resource from dockerhub using image digest | charmcraft | closed | Closed by maintainer facundobatista as superseded: charmcraft 1.1.1 (in candidate at the time) reworked OCI uploads to push images from the local machine and always reference them by digest, so the reported remote-digest limitation no longer applied. | |
| #1953 Charmcraft 3 should still accept image digests for `upload-resource` | charmcraft | open | Maintainer-filed Charmcraft 3 bug remains open: upload-resource still rejects bare OCI digests because Docker lookup returns only image IDs; no resolving change is present. |