How Docker Compose migrates startup directories

I have a docker-compose.yml file in directory a, and then I start the container with docker-compose up, and then I want to migrate the Docker Compose to directory b for management. what should I do?

as a beginner of Docker, I don"t quite understand the principle of Docker Compose. Because there is important data in this docker-compose project, I am afraid that data will be lost in the process of migration. When I search for the word "Docker Compose migration", I basically teach docker save and docker export backup images and containers, not how to migrate Docker Compose projects. However, when reading the article, I also mentioned the concept of container volume. Exponential data volume is independent of the image and container and has its own life cycle. It is necessary to mount the backup data volume after restoring the backup container. Maybe my understanding is not very correct, does it take so much effort to migrate the Docker Compose project?

I"m just working on this machine to change a directory for docker-compose, but I really can"t find the relevant tutorials on the Internet. It"s certainly useless to move docker-compose.yml files, and I don"t see any clue in the official website document https://docs.docker.com/compo.... Is it because I"m thinking too complicated?


the path of build and the path of volumes are relative paths. If so, just change it

.
MySQL Query : SELECT * FROM `codeshelper`.`v9_news` WHERE status=99 AND catid='6' ORDER BY rand() LIMIT 5
MySQL Error : Disk full (/tmp/#sql-temptable-64f5-7c1b32-2a8d0.MAI); waiting for someone to free some space... (errno: 28 "No space left on device")
MySQL Errno : 1021
Message : Disk full (/tmp/#sql-temptable-64f5-7c1b32-2a8d0.MAI); waiting for someone to free some space... (errno: 28 "No space left on device")
Need Help?