Replies: 2 comments
-
|
Good catch, and you've actually found a display bug here. The precedence order is:
What you're seeing: Your Dozzle container has no I'll fix that display bug so the detail view accurately reflects the effective policy and its source (e.g. "auto (from global default)"). To answer your question directly: if you want Dozzle to be manually updated, the easiest way is to set it in the container detail page in the web UI. That creates a per-container override that takes priority over everything else. You could also add |
Beta Was this translation helpful? Give feedback.
-
|
The display bug mentioned above has been fixed in v2.9.1 (#57, PR #61). Containers without a The precedence chain displayed in the UI now matches what the engine actually does:
|
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I am pretty sure I saw that somewhere in the documentation but could not find it anymore.
The dozzle container (just an example - this is the case for all containers) updates on its own because the global setting is "auto":
When looking at its details, though, it is set to "manual":
I am a bit confused by the cascading overwrites: doker label vs individual setting in the web UI vs global setting. Which one wins?
If I wanted to have dozzle being upgraded manually, where would I need to set it? Would that be reflected on the Web UI (like it is now, but with the "incorrect" setting?)
Beta Was this translation helpful? Give feedback.
All reactions