containerd charm configure to support for unsecure private registry (http)
Bug #1872949 reported by
Zhanglei Mao
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Containerd Subordinate Charm |
Fix Released
|
Medium
|
Unassigned |
Bug Description
The private registry shared by http ( not https) can not be used or correctly configure via
juju config custom_registries configure option
To reproduce it as:
juju config custom_registries a http private registry
and create a pod with it, it would still try to download with https and failed.
Changed in charm-containerd: | |
status: | New → Confirmed |
Changed in charm-containerd: | |
importance: | Undecided → High |
status: | Confirmed → Triaged |
Changed in charm-containerd: | |
importance: | High → Medium |
To post a comment you must log in.
Unfortunately this behavior is caused by a bug in containerd, see https:/ /github. com/containerd/ cri/issues/ 1433.