Self Hosted

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

Apr 30, 2024, 18:00

View on Discord

Votes

Replies

Participants

Unknown

Messages

khashashinOriginal post

Rank 1: Thread

Apr 30, 2024, 17:23

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

Summary

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

Rank 1: Thread

Apr 30, 2024, 17:24

khashashin

Rank 1: Thread

Apr 30, 2024, 17:26

Here is my docker-compose file

Ernest

Apr 30, 2024, 17:39

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

Ernest

Apr 30, 2024, 17:39

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

khashashin

Rank 1: Thread

Apr 30, 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:

⠴ 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

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

Need support?_