-
-
Notifications
You must be signed in to change notification settings - Fork 274
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Multiple Dockge instances #200
Conversation
Nice one. Coolify does this, too. |
@louislam This is an awesome product! Love it! I love this feature, too. Do you think it will be difficult to add filter options based on agents? That will be helpful if the same docker instances are running on multiple hosts. for example, I want to see only docker containers from a specific host/dockage agent ( i.e., current ). You really design nice UI, so I will leave the implementation to you ( if you are interested in this feature ). My suggestion is maybe a check box in the dockge agent section. or maybe a click on a flair to filter? |
I had a question regarding this, can you only connect in a one-direction fashion? Like I connected very simply from a newly created 2nd Dochge instance on another machine to my first, but then I log into my first one, and I try to connect IT to the SECOND one, and it times out. Is this normal? Am I supposed to just have one cental one and have it connect to all the others? Or am I just missing something? EDIT: Nevermind, I figured it out. My second instance was on my proxmox server on an SDN. Even though I had a static route in my router to point to my PVE host for this second subnet, I had to manually add an IP Route to my Linux machine in my main LAN for it to get there I guess. Leaving this up in case anyone else has this issue, but feel free to remove. |
Similar to Portainer agent approach.
A Dockge can connect to other Dockge instances.