#Docker containers not starting (no such file or directory)

4 messages · Page 1 of 1 (latest)

tepid egret
#

I'm trying to make a pull request, and I've followed the contribution guide, but most of the Docker containers aren't starting.
https://github.com/appwrite/appwrite/blob/master/CONTRIBUTING.md#setup-from-source

I've attached a full log file, but here are some interesting lines I've found. All the stopped containers I have seen are experiencing this 'no such file or directory' error. This is with a clean clone of master branch. The last command I executed was docker compose up -d

2023-02-28 00:12:32 appwrite-executor | exec /usr/local/bin/executor: no such file or directory
2023-02-28 00:12:38 appwrite-traefik | time="2023-02-28T08:12:38Z" level=warning msg="Could not find network named 'appwrite' for container '/appwrite'! Maybe you're missing the project's prefix in the label? Defaulting to first available network." container=appwrite-appwrite-af3fd248577c77d5e473cc5596ac7832d0841a37dc9f6b600db25b8411584c5b serviceName=appwrite_api providerName=docker

GitHub

Secure Backend Server for Web, Mobile & Flutter Developers 🚀 AKA the 100% open-source Firebase alternative. - appwrite/CONTRIBUTING.md at master · appwrite/appwrite

burnt rune
#

Hey 👋 Hmm that's weird. Can you try these commands to see if that helps?

git submodule update --init --recursive
docker compose build
docker compose up -d --force-recreate

One rebuilds console, one rebuilds Appwrite, one forcefully restarts Appwrite

#

I am not familiar with error you are getting so my guess would be some missing files in the build. So rebuilding might help.

tepid egret
#

I have ran both of those commands with the same result. Quite sad. I wanted to contribute. 😢