this post was submitted on 12 Oct 2023
0 points (50.0% liked)

Self-Hosted Main

515 readers
1 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

For Example

We welcome posts that include suggestions for good self-hosted alternatives to popular online services, how they are better, or how they give back control of your data. Also include hints and tips for less technical readers.

Useful Lists

founded 1 year ago
MODERATORS
communick@selfhosted.forum
0
How to migrate containers to portainer so I can get rid of the "limited control" portainer has over my containers? (alien.top)
submitted 1 year ago by Bwall19@alien.top to c/main@selfhosted.forum
5 comments fedilink hide all child comments
 

As stated. I stood up about 8 containers using docker desktop. Eventually I realized Portainer would be more useful and they now have an app for iphone. Once I installed it, portainer has "limited access" to my containers because they were created outside of portainer. Is there a way to fix this or do I have to re-build these in Portainer?

โ€‹

If so, I have a few Docker containers that I need database data from that I really don't want to lose. Is there a way to back up the data, and then re-create the same container from a backup in Portainer?

Still new to docker.

you are viewing a single comment's thread
view the rest of the comments
[โ€“] professional-risk678@alien.top 1 points 1 year ago

I would imagine you would have to rebuild them in portainer.

The good news is that portainer allows you to deploy either standalone containers or use docker-compose (portainer calls it stacks). So if you spin up said containers again and they have data paths that you can replicate, you should be able to just move your data over to the correct path on the new container that you have created

(random) Example: docker run -d -p 80:80 -v /some/path/to/content --restart unless-stopped somecompany/someapp:latest

If you were migrating that app you would need to just put the data back into the proper place (/some/path/to/content) for the container to recognize it. It would take some careful file transfers but it is DEFINITELY possible.

The bad news is that I dont know or understand the nature of your containers so im not sure what is needed specifically or where the containers were sourced/compiled from. Databases can be a bit trickier because they can be standalone dbs or they can be deployed with docker-compose alongside other containers as a service. You are going to have to work that bit out.