Dockge Updating Own Instance Causes it to not Restart Correctly

[oliv10]

⚠️ Please verify that this bug has NOT been reported before.

• I checked and didn't find similar issue

🛡️ Security Policy

• I agree to have read this project Security Policy

Description

Not entirely certain this is a bug or more of a feature request, but if you place the dockge stack within the stacks directory it can actually manage itself without issue unless you want to make changes to the dockge instance itself. Basically everything works as expected except for when you try and update the container configuration.

I can move this to a feature request if asked. Not that this is something a normal install would need to do regularly it would be cool if it could do it.

👟 Reproduction steps

Run an instance of dockge with itself inside of the stacks directory. Make changes to the dockge compose file within the app and save. Update and watch it shutdown and never return.

👀 Expected behavior

Dockge container shuts down and restarts with the new configuration.

😓 Actual Behavior

Dockge container shuts down and does not start back up again.

When trying to restart the container manually we have this, however it only happens on the first try of the command, the next time give the expected output.

root@dockage:/mnt/stacks/dockge# docker compose up -d
[+] Running 0/0
 ⠋ Container dockge  Recreate                                                                                                                                                                                                                                           0.0s 
Error response from daemon: Conflict. The container name "/7bd0176fc5ff_dockge" is already in use by container "8ce577eebf24bf0235468dfbd351ddd2ba266bebe28cc313659e256f27075b46". You have to remove (or rename) that container to be able to reuse that name.
root@dockage:/mnt/stacks/dockge# docker compose up -d
[+] Running 1/1
 ✔ Container dockge  Started                                                                                                                                                                                                                                            0.1s 
root@dockage:/mnt/stacks/dockge# 

Dockge Version

1.3.3

💻 Operating System and Arch

Ubuntu 22.04.3 LTS x86_64

🌐 Browser

Google Chrome Version 120.0.6099.71 (Official Build) (arm64)

🐋 Docker Version

Docker version 24.0.7, build afdd53b

🟩 NodeJS Version

No response

📝 Relevant log output

No response

[louislam]

Self manage is not possible right now due to technical issues, because Dockge killed itself during update.

[GamerClassN7]

I ma also interest in this feature, You could just spawn small little container and restart it from with in ? similar way Yacht do it () and after update again delete the container ?

[louislam]

Wow, I love your idea.

[oliv10]

Thats a neat work around. My first thought is how do you determine whether the container need to be restarted in this way or the standard way already implemented? Basically, how do you determine whether this is the dockge container we are restarting or not? IDK how to do this off the top of my head, but it was my initial thought.