Because the documentation says you can migrate from 0.2 to 1.0 but not from 0.2 to 2.0, I had installed a working 1.3.3 version with functions. I attempted to install 1.4.5 and recall an http error. Went ahead and migrated. I updated the main to include the context param per the docs. When building the function from the CLI, I get
[Error] Message: Docker Error: Unable to find image 'openruntimes/dart:v2-2.19' locally
docker: Error response from daemon: manifest for openruntimes/dart:v2-2.19 not found: manifest unknown: manifest unknown.
See 'docker run --help'.
[Error] File: /usr/local/app/http.php
[Error] Line: 603
[Error] Type: Exception
[Error] Message: Runtime not ready. Error Msg: []
Error: No such container: appwrite-executor-myprojectname-652e32f3452cc185a558-build
[Error] File: /usr/local/app/http.php
[Error] Line: 319
At some point I ran docker pull openruntimes/dart-2.19 (not exact image name).
- Is there an exception to successfully upgrade from minor versions to major ones.
- I do have a backup of the 1.3.3 data. 3). Thanks for any pointers.
[Error] Message: Docker Error: Unable to find image 'openruntimes/dart:v2-2.19' locally
2.2.19 is not in the list of images
I don’t have 2.19 in the ENV for Functions. I have 2.18,3.0
You jumped from 1.3.3 to 1.4.5?
At this moment I don't recall how I upgraded to 1.4.x. Yesterday I took my time and went 1.4.2 > 1.4.3 > 1.4.4, etc up to 1.4.7 (ran migrations too) I do recall deleting a non working function in the console. Then with the CLI, deploying it again.
Recommended threads
- problem with my function deployment
Hi, I'm using Appwrite Cloud in the fra region. I'm having an issue with Function domains. Functions deploy successfully. Executions from the Appwrite Console...
- image: openruntimes/executor:0.25.1 erro...
*this issue is not new and did happen on older versions using 0.7.22 removes the issue log ```ruby #2 /usr/local/app/http.php(78): Utopia\Http\Http->start() ...
- Executor with custom S3 doesn't work in ...
Was testing to upgrade appwrite to 1.9.5 and when testing the S3 part i saw the executor didn't work anymore. When looking closly i saw the `StorageFactory` doe...