Attempting to pull missing image from insecure registry fails

Bug #1839649 reported by Joseph Borg on 2019-08-09
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Containerd Subordinate Charm
High
Joseph Borg

Bug Description

Accumulating:
    https://github.com/containerd/cri/issues/1201
    https://discourse.jujucharms.com/t/cant-create-pod-with-container-from-a-custom-registry

Containerd via CRI fails to pull from a plain HTTP or plain HTTP with basic auth registry. This seems to be a bug in containerd.

Error:
    Failed to pull image "172.31.55.16:5000/nginx:latest": rpc error: code = Unknown desc = failed to resolve image "172.31.55.16:5000/nginx:latest": no available registry endpoint: failed to do request: Head https://172.31.55.16:5000/v2/nginx/manifests/latest: http: server gave HTTP response to HTTPS client

Joseph Borg (joeborg) on 2019-08-09
Changed in charm-containerd:
status: New → Triaged
importance: Undecided → High
Joseph Borg (joeborg) wrote :
Changed in charm-containerd:
assignee: nobody → Joseph Borg (joeborg)
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers