🎉 feat: Multiple docker endpoints

[mhkarimi1383]

@louislam
Hi
I found this project awesome, but a simple thing that is missing is managing multiple instances/servers

So, I have some ideas for that, by setting correct env vars when needed, etc.

[louislam]

Thank you!

Yes, multiple docker hosts feature is definitely a must have feature for this project.
It will be very similar to Portainer's agent, I think.

Of course, let's see if people love my idea of Dockge first.

I will keep testing this project for a while. And I will post it to https://www.reddit.com/r/selfhosted/ later if it is stable.

[louislam]

Just realize it is a pull request.

Actually we have Docker host config page in Uptime Kuma, I think I will copy this page to this project, no need to make a new one.

[mhkarimi1383]

@louislam

Yeah a copy from uptime kuma is awesome.!

So, I will wait for you to add UI :)

[louislam]

And I will post it to https://www.reddit.com/r/selfhosted/ later if it is stable.

Just posted to reddit, hope people will love it. 🐻
https://www.reddit.com/r/selfhosted/comments/17tkq79/dockge_a_fancy_easytouse_selfhosted_docker/

[Zaid-maker]

Just posted to reddit, hope people will love it. 🐻 https://www.reddit.com/r/selfhosted/comments/17tkq79/dockge_a_fancy_easytouse_selfhosted_docker/

Love the People responses!

[mhkarimi1383]

@louislam
Hi
You will copy Uptime Kuma UI? Or do I have to do it?

[louislam]

@louislam Hi You will copy Uptime Kuma UI? Or do I have to do it?

docker-compose on remote hosts is not that straightforward, I think it has to be studied first.

[mhkarimi1383]

@louislam Hi You will copy Uptime Kuma UI? Or do I have to do it?

docker-compose on remote hosts is not that straightforward, I think it has to be studied first.

I have some experience on that

It should be Ok since we are using commands in this project 😁

[mhkarimi1383]

@louislam
Hi
Any updates on UI?

[louislam]

I have studied a bit. Although we can docker-compose via Docker API(tcp://:2375)/Sock, it cannot create compose files or the stacks dir on the remote server, which is not something that I wanted.

So my direction will be SSH or an Agent.

I think the foundation of this feature should leave to me, I need a very clear plan before we go.

[mhkarimi1383]

I have studied a bit. Although we can docker-compose via Docker API(tcp://:2375)/Sock, but it cannot create compose files or the stacks dir on the remote server, which is not something that I wanted.

So my direction will be SSH or an Agent.

I think the foundation of this feature should leave to me, I need a very clear plan before we go.

Oh

Like K8s We could follow control-plane/worker setup
So, dockge server will be able to act just like a CP and others are workers (but CP could be usable as a worker for minimal setups)

OR

We can Switch to SSH

But it will be hard to have file manager

[cfpwastaken]

it cannot create compose files or the stacks dir on the remote server, which is not something that I wanted.

on my setup, i mounted the stacks directory on the other server with nfs, thus creating a file on server 1 will add them on server 2 too. Could be an idea to do something like this for now?

[gbrandt1]

Hello, I want to make a comment:
It would be good to support docker contexts which are built into docker instead of a custom solution like portainer.
This you can keep the dockge / shell equivalency and do not add a custom layer

https://docs.docker.com/engine/context/working-with-contexts/

[mhkarimi1383]

Hello, I want to make a comment:
It would be good to support docker contexts which are built into docker instead of a custom solution like portainer.
This you can keep the dockge / shell equivalency and do not add a custom layer

https://docs.docker.com/engine/context/working-with-contexts/

But how do you want to manage your stacks?

[gbrandt1]

But how do you want to manage your stacks?

so, i realize this is not feasible for every setup to do but at my work i have identical machines and i set up password-less ssh login and replicated the directory files exactly on the remote machine. then they were seemless to use with --context.

but i see docker realized this is not trivial as well so they removed the context option from docker compose for V2.

[mhkarimi1383]

@gbrandt1

You are correct if we do not manage our stacks using this project

@louislam

What about saving stacks in DB (not volume) in a compressed format?

When the UI updates a stack we will update the database, also we have a background job that keeps stack files up to date.
And create files on startup, also remove files on shutdown

[louislam]

Saving in db is not the direction of this project. People love Dockge because of file based and we don't kidnap users' compose files.

Also docker contexts is not able to save the compose files in the target server, so it is not the direction either.

I am implementing the agent mode in #200 which basically keeping Dockge's current design, but adding ability to manage all Dockge instances in one single Web UI.