
I am trying , again , to upgrade my server (currently in production in version 1.4.9) to 1.5.7
I am following a very strict roadmap, Upgraded to 1.4.14 and migrated - all good. When upgrading from 1.4.14-1.5.0:
- It is running and pulling all images
- downloading all sorts of things (~500 MB)
- removing some containers (displayed in red in the console)
- starting many containers (again, in red) and then , I get this msg.....
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
I guess it suggest something is mission in my $PATH (Ubuntu 22.04.3 LTS) by I could not figure out what and why.
And then it stops.
I dont know if it means the update failed. Please help.
Update: I have gone and ran the migration after completed successfully, I ran
docker compose up -d
and it returned somehow same error
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

It seems that something in the "appwrite-worker-usage" was causing the problem, the entrypoint for this container was "usage" that was not found!
I have gone and upgraded from 1.5.0 to 1.5.7 and it seems that in 1.5.7 everything is working
Recommended threads
- Getting Error On self host SSL update
Hi, I am using app write for my app backend version i am using is 1.6.2 yesterday my ssl is expired and now i am not able to renew it because of it my app is no...
- import csv "Document already exists"
When I try to import a csv file to an already existing database, I keep getting "Document Already Exists" I thought that when I import and a document with the ...
- Can not migrate to self hosted instance ...
Hey! I want to migrate from Appwrite Cloud to a self hosted instance and it's a really frustrating journey for now. Exporting itself does not work, so I did w...
