BloodThermicOriginal post
Rank 3: Container
When I run this command docker-compose exec -T mariadb sh -c 'exec mysql -u"$MYSQL_USER" -p"$MYSQL_PASSWORD"' < dump.sql
I get this error. The file is uploaded and named accordingly
ERROR: The Compose file './docker-compose.yml' is invalid because:
Invalid top-level property "x-logging". Valid top-level sections for this Compose file are: version, services, 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/```
I am following this guide.
https://dev.to/appwrite/appwrite-in-production-backups-and-restores-4beg
I was able to create the dump file but cant restore it .
Summary
User is experiencing an error when trying to restore a backup in Mariadb. They ask if they can change the username and password for the database, and are told that they cannot change those values after the database has started. They eventually reset the password and are able to login, but encounter an issue where they are logged out when trying to access the web panel. They are advised to uninstall the old version and update to Docker compose v2. They mention their Docker version as 24.0.2 and their Docker compose version as 1.25.0. They receive an error when trying to run a command to restore the backup,