proxmox, lxc, ansible use-case(s) #365
jschneekloth
started this conversation in
Feature Request
Replies: 1 comment
-
Hi @jschneekloth, |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
🏷️ Feature Request Type
Other
🔖 Feature description
Apologies for this being a bit of a catch-all and not specific to a single feature request as well as the amount of text here....
Also, thanks so much for all the work done to date on uptime and dockge, these are both truly innovative services and love them both! Let me first describe my use-case and then what I would love to see from Dockge in order to better support that use-case which I also feel would be useful to many other use-cases as well. My setup is as follows. I use proxmox as my hypervisor and auto create new LXC's (or VMs) for new services in my home lab. On each LXC, I install docker and then use docker compose to manage the service(s) that LXC serves. For example, I have a monitoring LXC, that I use docker (compose) to deploy grafana, prometheus, influxdb, and uptime-kuma for holding metrics and driving alerts for the overall home lab itself. I use ansible for creating and managing the LXC and docker compose for defining what is on each lxc so I can push it all to source control and rebuild the world at-will if ever needed, not to mention things like tracking changes to services rollbacks and anything else that by such a workflow. It's worked really well so far. What I have found lacking, however, is a centralized and visual way of tracking all the containers/services across everything in the home lab. What I have seen from Dockge so far is SO CLOSE to perfection for this use case!!
Here's what I've played with so far:
I manually went through this process (via ansible) and created the "dockge-master" lxc that I would expect the agents to roll up to now that I see that's a thing (awesome btw) and I've updated an existing LXC to by dockge first...which means I do the following:
And this works! I can then go to dockge url, create username/password, manually add it to the "single" manager via the agent and manually start the discovered docker compose. This is a great step forward in my overall experience. Now....here is how I view this overall UX can be improved, and I suspect this is more globally useful than specific to how I want to use Dockge as well (I think in priority order from my perspective).
I think with above alone, are more precise and manageable workflow can be supported.
More general quality of life improvements:
Thanks again for everything in this project and uptime! Happy to walk through my use case in more detail as well...
✔️ Solution
no solution explicitly, just starting a convo
❓ Alternatives
No response
📝 Additional Context
No response
Beta Was this translation helpful? Give feedback.
All reactions