WildAnimalOriginal post
Rank 2: Process
According to https://gist.github.com/Meldiron/47b5851663668102a676aff43c6341f7
Backup the datas from appwrite 1.3.1 and restore to appwrite 1.3.4.
After completing the above operations I run the "docker-compose up -d" command to restart containers got warn:
WARN[0000] volume "[volume name]" already exists but was not created by Docker Compose. Use `external: true` to use an existing volume
At this point, the restored data did not take effect.
Then I added "external: true" under each volumes in yml file:
YAML
volumes: appwrite-mariadb: external: true appwrite-redis: external: true appwrite-cache: external: true appwrite-uploads: external: true appwrite-certificates: external: true appwrite-functions: external: true appwrite-builds: external: true appwrite-influxdb: external: true appwrite-config: external: true appwrite-executor: external: trueRun "docker-compose up -d" again got errors:
external volume "[voleme name]" not found
This seems to be contradictory, where is the problem.
Summary
The user is experiencing issues with migrating data from Appwrite 1.3.1 to 1.3.4. After restoring the data and restarting the containers, they receive a warning message stating that the volume already exists but was not created by Docker Compose. To fix this, they added "external: true" under each volume in the YAML file. However, when running "docker-compose up -d" again, they encounter an error stating that the external volume was not found. The user is unsure about the source of the problem.
Solution: It appears that the volumes were not properly created or named. Check if the volumes