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
- Dockerizing Appwrite Console Yields Page...
I have this Docker Compose file: ``` services: # Band9Buddy app band9buddy: build: context: . dockerfile: Dockerfile.dev develop: ...
- Upgrading Appwrite 1.7.4 → 1.8.x: What H...
I'm currently running a self-hosted Appwrite v1.7.4 instance that still uses the old Collections/Documents database model. I noticed that starting from v1.8.x,...
- Domain not working
My domain [fork-fable.appwrite.network](https://fork-fable.appwrite.network/) returns a 500 even after deleting and redeploying. Other domains added in domains ...
