Lost stacks about dockge

[urolithicrogue]

did you run the two commands separately? i had a similar issue till i realized the commands needed to be run separately.

basically what happened if you ran the commands together, instead of reading from /opt/dockge like it should it would have instead ran from the / directory. running the commands again but separately should update dockge correctly and make your stacks show back up assuming that they are in the default directory of /opt/dockge.

(it looks like one command because of having no space in between but is actually 2 commands like so)

cd /opt/dockge

docker compose pull && docker compose up -d

[glennpierce]

I ran the command together. Copied and pasted from the Readme. I have done the same in the past with no problem.
The default location in my case was /opt/stacks/
My files were actually wiped from the filesystem . The only one left was one from the service gotify
which was a docker service I did not have managed or running by dockge. That may be a clue ?

I must confessed as I had to recreate all my service compose files I have lost confidence and just decided to use compose / docker on the command line now.

Thanks

[PatNei]

This happened to me to. I stopped and removed all the docker containers and now it can't even detect the stacks in the folder. I never changed any setting, it is very strange.