I have 27 containers running with rancher on windows. Long story short, I’m tired of the resource use and stress on my machine by running the VM. My data folders are split up by duty (admin, utility, media, virtualization) each duty has its own folder, containing the services’ folder with data/config directories and one compose.yaml file for those services. All the compose files are connected to a master compose file in the parent directory that starts all of them. My compose files have references to the media hdds that are defined with an .env file next to the master compose.
I need to clone my docker setup to a Debian install I’ve been working on on its own ssd. I’ve been screwing with Linux unsuccessfully for almost 20 years, so my cli is weak. I’m looking for a tool that will clone my volumes and containers.
What do you use?
carrylex@lemmy.world
Botzo@lemmy.world 2 days ago
rsync
Built-in, picks up where it left off if you accidentally cancel it by running the same command again, and dead simple.
Permissions for the files will probably be a little broken moving to Linux, but chmod is also easy to use and can work at the directory level.
lambalicious@lemmy.sdf.org 2 days ago
Be wary when you use rsync, to not upgrade past version 3.4.1. Later versions were vibecoded / slopecoded and cause data loss.
confusedpuppy@lemmy.dbzer0.com 2 days ago
I too was upset with the use of Claude/AI/LLM’s in the rsync project. The maintainer received a lot of public backlash and as a result people have offered their time to help the maintainer with this project.
Since the backlash, the use of agents has been drastically reduced. That seems like a very human and overall positive response. It sucks that it happened. It’s nice that people are now doing the work again. The response could have been a lot worse. I can be forgiving in this specific situation.
frongt@lemmy.zip 2 days ago
Fuck’s sake. What was the actual bug introduced? I skimmed the issues on GitHub and nothing jumped out at me.
Botzo@lemmy.world 2 days ago
Dammit.
frongt@lemmy.zip 2 days ago
This. Docker compose down, schlep the data over, update paths and permissions, docker compose up. Done.
Probably bring it up one step at a time so you can more easily identify anything you missed.
Botzo@lemmy.world 2 days ago
If you need to change the references in the compose or env files: