jadechessinkOriginal post
Rank 1: Thread
Parent folder is /docker, appwrite is inside the /docker folder, inside of /docker/appwrite is my docker-compose.yml.
ran the following to update appwrite:
docker run -it --rm --volume /var/run/docker.sock:/var/run/docker.sock --volume "$(pwd)"/appwrite:/usr/src/code/appwrite:rw --entrypoint="upgrade" appwrite/appwrite:1.3.0
Tried manually specifying the folder:
docker run -it --rm --volume /var/run/docker.sock:/var/run/docker.sock --volume /docker/appwrite:/usr/src/code/appwrite:rw --entrypoint="upgrade" appwrite/appwrite:1.3.0
both resulted in the following errors:
docker: Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "upgrade": executable file not found in $PATH: unknown.
i can confirm this was run from the parent "/docker" folder as specified in the directions.
i also tried to run it with other versions of appwrite 1.3.x and it also failed. Docker-compose.yml has been minimally changed to facilitate some volume binding. docker-compose attached.
Just wanted to know if this is due to me changing the volumes in the docker compose, or if theres some other issue at play here, and if there is, what it might be.
Summary
Summary: The user encountered issues while upgrading from Appwrite 1.2.1 to 1.3.0. They found that the issue was a misconfiguration of the openssl key in the .env file. The user also had trouble logging in after the upgrade and suspected a problem with their docker volume binds. To troubleshoot, they were advised to check the console users table in the database and try reloading Docker. The user also asked if there was a way to reset their password from the CLI.
Solution:
1. Compare the current .env file with the previous one to ensure the openssl key is correct.
2. Connect