• 0 Posts
  • 1 Comment
Joined 1 year ago
cake
Cake day: October 12th, 2023

help-circle
  • 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.