Cannot override docker.io
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Containerd Subordinate Charm |
Fix Released
|
High
|
George Kraft | ||
Bug Description
In an offline deployment, we want the default docker.io registry to point to our private registry.
If I set custom_registries set to:
[{"host": "docker.io", "url": "https:/
Then a subsection of config.toml looks like:
endpoint = ["https:/
[plugins.
endpoint = ["https:/
Ignoring the messy indentation, this seems like it might work but the charm's workload status is blocked with "Container runtime not available" and when trying to start containerd manually we get:
containerd: failed to load TOML: /etc/containerd
When there is a host docker.io in custom_registries, we must not write the default docker.io line.
| description: | updated |
| Vern Hart (vern) wrote | #1 |
| Vern Hart (vern) wrote | #2 |
| Changed in charm-containerd: | |
| importance: | Undecided → High |
| status: | New → Triaged |
| Changed in charm-containerd: | |
| assignee: | nobody → George Kraft (cynerva) |
| status: | Triaged → In Progress |
| tags: | removed: review-needed |
| Changed in charm-containerd: | |
| milestone: | none → 1.22+ck1 |
| status: | In Progress → Fix Committed |
| tags: | added: backport-needed |
| Changed in charm-containerd: | |
| status: | Fix Committed → Fix Released |
This is my simple solution. If there isn't a docker.io entry in custom_registries, I insert one. And then the template doesn't need any extra logic to figure out whether to output the docker.io host or not.