Attach existing volumes from migrated server #484
Replies: 1 comment
-
What I ended up doing is putting all my data into each stack directory. I figure that each stack is not fully self-contained so its easy to backup, restore or migrate. This also works really well if the underlying system is ZFS with snapshots.. can easily revert a single folder in case of problems. This also works really nicely with the GUI.
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
🛡️ Security Policy
📝 Describe your problem
I moved all my docker volumes from old server to new server.
I am new to dckge, ok - I want to create
uptime-kuma
using an existing volume - I created the volume usingdocker volume
I get the error
service refers to undefined volume invalid compose project
I have to manually update the compose file to look like this before it starts.
Maybe a UI option, like with networks on the right side to handle like volumes you add. you can change the check box to "external"?
Or have a drop down in the volumes bit to select existing volumes
I know this is the case.. usually you just want to bind to a directory that is easy for backup I guess.. but im migrating this is easiest option.
📝 Error Message(s) or Log
service refers to undefined volume invalid compose project
🐻 Dockge Version
there is no version displayed on the UI how am i supposed to know?
💻 Operating System and Arch
debian LTS
🌐 Browser
Edge
🐋 Docker Version
Latest
🟩 NodeJS Version
na
Beta Was this translation helpful? Give feedback.
All reactions