summaryrefslogtreecommitdiff
path: root/op-mode-definitions/monitor-bridge.xml.in
diff options
context:
space:
mode:
authorChristian Breunig <christian@breunig.cc>2024-02-23 21:49:50 +0100
committerMergify <37929162+mergify[bot]@users.noreply.github.com>2024-02-24 08:09:52 +0000
commitfcebadea51c1df88553e608a0866a6f2a1dcaa2b (patch)
tree49ce298230be3dfb53449cb65037b78ded92329a /op-mode-definitions/monitor-bridge.xml.in
parent9086748f7a3f83482f5c39ca2d611ec22b329296 (diff)
downloadvyos-1x-fcebadea51c1df88553e608a0866a6f2a1dcaa2b.tar.gz
vyos-1x-fcebadea51c1df88553e608a0866a6f2a1dcaa2b.zip
container: T5909: move registry login to op-mode
It does not make sense to perform the "podman login" command when setting up containers, as images are not automatically pulled in from the registry - due to issues with the default route during startup. The same issue manifests in "podman login" where we can not login to a registry unless there is a default route present. This commit changes the behavior that the container registry is part of the configuration, but it is only referenced during "add container image" and thus never during system boot. (cherry picked from commit baf30d8319ef4d0f0cc4cdf0f7c12f03f8a492b6)
Diffstat (limited to 'op-mode-definitions/monitor-bridge.xml.in')
0 files changed, 0 insertions, 0 deletions