appwrite: πŸ› Bug Report: All function files are deleted when the container is stopped

πŸ‘Ÿ Reproduction steps

  1. Deploy a cloud function for a project (Just a simple Hello World output)
  2. Run docker-compose down
  3. Run docker-compose up -d
  4. Try to execute the function. There will be an error with the string: File Not Found
  5. Deploy the same function again
  6. Now executions are working

πŸ‘ Expected behavior

I would expect that after rebooting the containers, you don’t have to redeploy all the functions every time. For large projects, that could be a lot.

πŸ‘Ž Actual Behavior

Currently, you have to redeploy the functions after each container restart. Otherwise they do not work and return β€œFile not found”. The programming language of the function does not seem to matter. I tested it with DART and PHP functions.

🎲 Appwrite version

Version 0.13.x

πŸ’» Operating system

MacOS

🧱 Your Environment

No special customizations.

πŸ‘€ Have you spent some time to check if this issue has been raised before?

  • I checked and didn’t find similar issue

🏒 Have you read the Code of Conduct?

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Comments: 17 (11 by maintainers)

Most upvoted comments

Found it πŸ₯³ We will need to sync our development and production docker-compose, as there are some mismatches around volumes, environment variables, and versions.

The solution to this problem can be seen in this gist: https://gist.github.com/Meldiron/1ac493328141210da950e40d9c3cb568/revisions

Check out the latest revision and apply these changes to your docker-compose.yml. Then, restart appwrite with docker-compose down && docker-compose up -d. After Appwrite starts, make sure to redeploy your functions, and from now on, your functions should not lose deployments if you restart Appwrite 😍

CleanShot 2022-03-16 at 10 24 02

Never mind, the problem is there on 0.13.2, but not on master branch. With next release, the bug will most likely be fixed.

i can confirm, everything is fine now! πŸ˜‰

I can confirm this occurs with 0.13.3 when using Docker images. If started from source code (same version), it works fine. Whoof, this one will be interesting… πŸ€”