Migration from 1.4.13 to 1.5.5 Error response from daemon: failed to create task for container
- 0
- Self Hosted
After upgrading appwrite in my docker-compose.yml and running the docker compose up -d --build I get the following error:
Here is my docker-compose file
Did you not use the update command? i.e. docker run...
If you did, then did you run the migration command?
Ok. I see... thanks!
I can't run the command docker run ... from the appwite upgrade docs sinse I use appwrite under custom traefik instance and have to pass the labels.
But I ran now the command docker compose exec appwrite migrate and the migration completed successfully. Now I can login in to my appwite console.
However I still get the error after docker compose up -d --build:
⠴ Container appwrite-schedule Starting 0.5s
⠴ Container appwrite-usage Starting 0.5s
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: "usage": executable file not found in $PATH: unknown
Recommended threads
- function subdomain ssl certs
The generated subdomain isn't getting a valid ssl cert, I was wondering if appwrite automatically generates one or uses a wildcard for *.functions.domain.com? ...
- Whats best practise for Appwrite Cloud?
Appwrite Teams map very nicely to my needs, it is how i group users together. ... I use roles to define permissions. Should I also map a table to each team ? ...
- Error getting preview of file
Rest Response: ``` { "message": "Server Error", "code": 500, "type": "general_unknown", "version": "1.8.1" } ``` Appwrite Logs ``` appwrite ...