Repository navigation
|
I'm looking to implement the following update scenario: I'm struggling to get this scenario to work For my Drydock controller I have the following (Datavault is the name of my server):
(I have the same for my agents but with their respective server names) For the containers I want to auto-update, I have the following label: Any ideas on what I'm doing wrong would be greatly appreciated |
Replies: 3 comments 2 replies
|
|
|
Thanks for the response @junkerderprovinz. The issue I have with this "Under onauto a container without any label is blocked rather than manual, so give the ones you want to update by hand dd.action.include=datavault" is that means I have to add a .include action to every container that I want to manually update which seems like overkill - plus any future containers I want to manually update I would also have to include that label. @scttbnsn is there any functional way to just default all containers to manual and only add labels for the containers I would like to auto update? That way I don't have to constantly manage labels for all containers only the ones I want to auto update. One could argue the opposite scenario would be helpful if not already possible - set all containers to auto and just exclude ones that you want to be manual. Thanks! |
|
You can't get that with one Docker action today. You're right about the gap: On the 1.7 release candidates, there is a two-action workaround. On DataVault, keep the automatic action and add a separate manual fallback: Then keep Repeat the two actions on each agent, using that host's action name in the auto label. Actions need to be configured on the instance that watches the container. I've checked the policy selection in both registration orders: unlabeled containers get manual access, and the automatic path selects the opted-in action. This is a code-level check, not a live update test. It does emit the equally-specific-actions warning, and registration order can affect which action the UI shows for an opted-in container. That's a workaround with rough edges. I've put the single-action manual-default gap on the roadmap. |
You can't get that with one Docker action today. You're right about the gap:
onautorequires labels for manual access too.On the 1.7 release candidates, there is a two-action workaround. On DataVault, keep the automatic action and add a separate manual fallback:
Then keep
dd.action.auto=datavaultonly on the containers you want updated automatically. Unlabeled containers can use the manual action without an include label. Set the global update mode toauto; globalmanualwould prevent the selected containers from updating automatically too.Repeat the two actions on each agent, using that host's action name in the…