Comment 6 for bug 1981335

To test this I got the image info and credentials from the resource (basically what Nikolaos did just with the docker client)

curl -sL https://api.charmhub.io/api/v1/resources/download/charm_Z2g5QvSCaQsxR3kKn0AwvNytkMgIhFrN.oci-image_26 | jq .

then I did:

docker logout
docker login registry.jujucharms.com

and I input the credentials (username, password) from the resource. I then did:

docker pull registry.jujucharms.com/charm/c2o31yht1y825t6n49mwko4wyel0rracnrjn5/oci-image@sha256:13c46cf878062fd6ad672cbec4854eba7e869cd0123a8975bea49b9d75d4e698

(the image identifier comes right from the resource as well).

This downloaded about 4GB worth of layers on a 30 Mbps residential connection. Took its sweet long time but it did work:

$ docker pull registry.jujucharms.com/charm/c2o31yht1y825t6n49mwko4wyel0rracnrjn5/oci-image@sha256:13c46cf878062fd6ad672cbec4854eba7e869cd0123a8975bea49b9d75d4e698
registry.jujucharms.com/charm/c2o31yht1y825t6n49mwko4wyel0rracnrjn5/oci-image@sha256:13c46cf878062fd6ad672cbec4854eba7e869cd0123a8975bea49b9d75d4e698: Pulling from charm/c2o31yht1y825t6n49mwko4wyel0rracnrjn5/oci-image
a16b311a57cb: Pull complete
d8f1984ce468: Pull complete
a6259a641324: Pull complete
08f1612b3894: Pull complete
6efd3ea758ec: Pull complete
d43a70c57613: Pull complete
fe09379c9a6e: Pull complete
92a1f997eb57: Pull complete
e2d89532c3ba: Pull complete
3db2b246fb42: Pull complete
562ba219afe4: Pull complete
6f369261a09f: Pull complete
977cd55548b1: Pull complete
2563eaea9368: Pull complete
35fdeb2cc87a: Pull complete
b28b2e05a521: Pull complete
c40f63038123: Pull complete
Digest: sha256:13c46cf878062fd6ad672cbec4854eba7e869cd0123a8975bea49b9d75d4e698
Status: Downloaded newer image for registry.jujucharms.com/charm/c2o31yht1y825t6n49mwko4wyel0rracnrjn5/oci-image@sha256:13c46cf878062fd6ad672cbec4854eba7e869cd0123a8975bea49b9d75d4e698
registry.jujucharms.com/charm/c2o31yht1y825t6n49mwko4wyel0rracnrjn5/oci-image@sha256:13c46cf878062fd6ad672cbec4854eba7e869cd0123a8975bea49b9d75d4e698

$ docker image list registry.jujucharms.com/charm/c2o31yht1y825t6n49mwko4wyel0rracnrjn5/oci-image
REPOSITORY TAG IMAGE ID CREATED SIZE
registry.jujucharms.com/charm/c2o31yht1y825t6n49mwko4wyel0rracnrjn5/oci-image <none> 913fc89e48ad 10 months ago 4.04GB

I did get the impression it was kind of slow. What could be happening here is that registry.jujucharms is slow and/or craps out mid-download. If this happens with a desktop client I can retry. I don't know what the behavior is with the kubernetes docker client. The data stored in the registry doesn't seem to be corrupted, so a download hiccup causing unrecoverable corruption sounds like a docker shortcoming rather than a registry problem.

My team doesn't directly operate registry.jujucharms.com, but I can check internally to see who is considered responsible for its operation and see if there are any metrics they could check or share to understand if the service is overloaded or having any kind of network trouble, and then scale or mitigate accordingly.