Replies: 1 comment 1 reply
-
I always add a Stack to manage Komodo Core. I run Periphery with systemd though, so Periphery isn't part of the Komodo Core stack. In this case, Komodo can redeploy itself, eg to update the version. The Update log will seem to fail due to Core restart, but Periphery is handling the redeploy, so it works despite the failed Update log. If refresh the page after a short time, you will see Core comes back up and the version has been updated. If you prefer to run Periphery in container, you can accomplish something similar by deploying Periphery container outside of the Core stack, maybe in its own dedicated compose file, or just using docker run command. In terms of managing Periphery version across many servers, I recommend an Ansible playbook for this. You can run Ansible in a container ( |
Beta Was this translation helpful? Give feedback.
-
Currently, komodo cannot manage its own stack. It's possible to execute the same actions as with other stacks, but some of those actions will fail (Redeploy, Restart) and others don't really make sense for a docker management tool (Pause, Stop, Destroy).
Maybe komodo could detect when a stack is using ghcr.io/mbecker20/komodo? It could then disable Pause, Stop and Destroy for that stack, and implement a workaround for Redeploy and Restart.
Dockge is faced with the same issue. Here is what has been proposed on their side:
Originally posted by @GamerClassN7 in louislam/dockge#288 (reply in thread)
What do you think?
Beta Was this translation helpful? Give feedback.
All reactions