Back

Backup Appwrite causes issues with docker-compose file

  • 0
  • Self Hosted
Butterbeerpop
1 Sep, 2024, 14:32

I am trying to backup my appwrite instance and it won't let me because of the following: " docker-compose exec mariadb sh -c 'exec mysqldump --all-databases --add-drop-database -u"$MYSQL_USER" -p"$MYSQL_PASSWORD"' > ./dump.sql ERROR: The Compose file './docker-compose.yml' is invalid because: networks.appwrite value Additional properties are not allowed ('name' was unexpected) networks.gateway value Additional properties are not allowed ('name' was unexpected) networks.runtimes value Additional properties are not allowed ('name' was unexpected) Invalid top-level property "x-logging". Valid top-level sections for this Compose file are: services, version, networks, volumes, and extensions starting with "x-".

You might be seeing this error because you're using the wrong Compose file version. Either specify a supported version (e.g "2.2" or "3.3") and place your service definitions under the services key, or omit the version key and place your service definitions at the root of the file to use version 1. For more on the Compose file format versions, see https://docs.docker.com/compose/compose-file/"

TL;DR
Developers are facing issues with backing up Appwrite due to errors in the docker-compose file. The error message indicates problems with the version or structure of the file. To resolve this, the developers need to either specify a supported version (e.g., "2.2" or "3.3") and place service definitions under the 'services' key, or omit the 'version' key and place service definitions at the root of the file to use version 1. More details on Compose file format versions can be found at the provided link.
Reply

Reply to this thread by joining our Discord

Reply on Discord

Need support?

Join our Discord

Get community support by joining our Discord server.

Join Discord

Get premium support

Join Appwrite Pro and get email support from our team.

Learn more