Back

Migration from 1.4.13 to 1.5.5 Error response from daemon: failed to create task for container

  • 0
  • Self Hosted
khashashin
30 Apr, 2024, 17:23

After upgrading appwrite in my docker-compose.yml and running the docker compose up -d --build I get the following error:

TL;DR
Developers upgraded from Appwrite version 1.4.13 to 1.5.5. After running `docker compose exec appwrite migrate`, the migration completed successfully but they faced an error when running `docker compose up -d --build`. The error message indicated an issue with the container creation process. Solution: Add the missing executable file 'usage' to the $PATH environment variable.
khashashin
30 Apr, 2024, 17:24
khashashin
30 Apr, 2024, 17:26

Here is my docker-compose file

Ernest
30 Apr, 2024, 17:39

Did you not use the update command? i.e. docker run...

Ernest
30 Apr, 2024, 17:39

If you did, then did you run the migration command?

khashashin
30 Apr, 2024, 17:47

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:

TypeScript
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
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