🚀 Feature Request: Updating dockge from within dockge

[BenJamesAndo]

The ability to click a link or button from within Dockge to initiate it updating itself to the latest version.
Portainer BE has this functionality. https://docs.portainer.io/start/upgrade#from-within-portainer

[x1ao4]

You can achieve this by putting Dockge's Docker Compose file into the stacks folder, allowing Dockge to manage itself.

[mahmoudhamadeh]

I tried this, it is not working unless I'm doing something wrong. I moved the opt/dockge folder inside opt/stacks, I can see Dockge stack now in the list. When I try to update, it is pulling the new image but failed to restart. The only way to restart it is going into the terminal under opt/stacks/dockge and run docker compose up.

[x1ao4]

Is your Dockge Compose file named /opt/stacks/dockge/compose.yaml? When I click update within Dockge, it automatically pulls the image and restarts successfully.

[Ashkaan]

What are the exact steps? Here's what I did:

1. Remove the current dockge instance
2. Added compose.yaml to /opt/stacks/dockge/compose.yaml
3. docker compose up -d on that folder

Inside, I get this message:

[x1ao4]

What are the exact steps? Here's what I did:

1. Remove the current dockge instance
2. Added compose.yaml to /opt/stacks/dockge/compose.yaml
3. docker compose up -d on that folder

Inside, I get this message:

You don't need to carry out the operations in Step 1 and Step 3. It seems that you've also made an error in the operation of Step 2 (the container name appears to be incorrect).

Please refer to the section "Can I manage existing stacks?" for instructions. Letting Dockge manage itself actually means having Dockge manage the Dockge container that wasn't created within Dockge. Just like other containers that weren't created within Dockge, there's no difference.

[Ashkaan]

Also, this happened. I'm not sure how to clear it. I've tried deleting the inactive ones, but that deletes BOTH dockge instances.

[Ashkaan]

Ahh! The name matters! That solved my issue.

Thank you so much

[lehades]

@x1ao4 @Ashkaan ¿Does this still work for you?

I just started using Dockge and i'm trying this and it doesn't seem to work: i have Dockge running and self-managing it's instance: i can stop it or restart it from the web portal.. but if i try to update it it just stops and never gets back up.

stacks folder is '/opt/stacks' and dockge folder is '/opt/stacks/dockge'

¿Am I missing something stupid?

[Ashkaan]

I'm not using Dockge anymore, but it always worked after fixing the naming issue.

[mahmoudhamadeh]

Due to the limited support, I have moved from Dockge to Arcane. I'm happy with the change since it has been working much better for my needs.

…

On Fri, 9 Jan 2026 at 08:11, Ashkaan ***@***.***> wrote: I'm not using Dockge anymore, but it always worked after fixing the naming issue. — Reply to this email directly, view it on GitHub <#213 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AGNOAIQV42K5MHVKOJPDZL34F6SJ5AVCNFSM6AAAAAB3DUWKZKVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTKNBVGQ3DMNQ> . You are receiving this because you commented.Message ID: ***@***.***>

[andreibrebene]

It will not work anymore because Docker Compose v5 is more aggresive with recreating containers. Until Docker compose v5.0.0 it worked for me too.