Replies: 2 comments 2 replies
-
I couldn't wait and took a stab at this ;) but it didn't work how I expected. On the command line and/or portioner:
Then used the dockge converter to convert this to a compose file: output compose.yaml file:
When I started it up, it asked me to create a new password so I new it wasn't seeing the original volume. I thought perhaps it was the network, but I couldn't seem to start on the same network so I exported the json from original instance and imported into the new dockge instance. I still have my original volume I'd be curious if there is a better way. |
Beta Was this translation helpful? Give feedback.
-
See this: https://github.com/louislam/dockge#can-i-manage-existing-stacks |
Beta Was this translation helpful? Give feedback.
-
I love uptime-kuma and this tool is awesome too! I already have 3 containers running on my test server, is there any way to import them into dockge? Do I need to expose the docker docket when starting up so they can be seen? I'd like to have this be aware of my uptime-kuma instance running on the same machine and then fire it up though dockge so I can control/upgrade from here with the yaml file moving foward. Is there an easy way to do this without destroying the existing uptime-kuma container, recreating yaml and firing it up again? Will my directories stay where they are and any data lost from the volumes if I do this?
Beta Was this translation helpful? Give feedback.
All reactions