docker registry charm ignores juju-http-proxy and juju-https-proxy
Bug #1832336 reported by
Calvin Hartwell
This bug affects 4 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Docker Charm Layer |
Fix Released
|
High
|
George Kraft | ||
Docker Registry Charm |
Fix Released
|
High
|
George Kraft |
Bug Description
Hi all,
The docker registry charm ignores the juju-http-proxy and juju-https-proxy variables which should now be used for handling proxy. The charm specific http-proxy/
The charm specific options should be given the default values of the the juju-http-
Feel free to ask questions.
summary: |
- docker registry charm ignores juju-http-proxy and juju-https-proxy + docker registry charm ignores juju-http-proxy and juju-https-proxy (its + being very naughty) |
Changed in layer-docker-registry: | |
assignee: | nobody → Kevin W Monroe (kwmonroe) |
status: | New → Triaged |
summary: |
- docker registry charm ignores juju-http-proxy and juju-https-proxy (its - being very naughty) + docker layer ignores juju-http-proxy and juju-https-proxy |
Changed in charm-containerd: | |
milestone: | none → 1.16 |
Changed in charm-docker: | |
milestone: | none → 1.16 |
Changed in layer-docker-registry: | |
assignee: | Kevin W Monroe (kwmonroe) → George Kraft (cynerva) |
Changed in charm-layer-docker: | |
assignee: | Joseph Borg (joeborg) → George Kraft (cynerva) |
Changed in charm-layer-docker: | |
status: | In Progress → Fix Committed |
milestone: | none → 1.16 |
Changed in layer-docker-registry: | |
milestone: | none → 1.16 |
Changed in charm-layer-docker: | |
importance: | Undecided → High |
Changed in layer-docker-registry: | |
importance: | Undecided → High |
Changed in layer-docker-registry: | |
status: | In Progress → Fix Committed |
Changed in charm-layer-docker: | |
status: | Fix Committed → Fix Released |
Changed in layer-docker-registry: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
The http/s-proxy config options come into the docker-registry charm because of the inclusion of layer:docker:
https:/ /github. com/CanonicalLt d/docker- registry- charm/blob/ master/ layer.yaml# L7
See the config opts defined in that layer here(ish):
https:/ /github. com/juju- solutions/ layer-docker/ blob/master/ config. yaml#L68
Managing these option with their corresponding juju- model config opts should be handled by that project.