Rank 3: Container
that means it can reach host now
Votes
1
Replies
24
Participants
Unknown
Messages
25
Rank 3: Container
that means it can reach host now
Try to deploy now
Rank 3: Container
% docker exec appwrite vars | grep _APP_EXECUTOR_RUNTIME_NETWORK
Something is not quite right
Rank 3: Container
Cannot access offset of type string on string
Rank 3: Container
what should in _APP_EXECUTOR_RUNTIME_NETWORK ?
Run
docker compose down
Then
docker ps -a
What you get
Rank 3: Container
empty list
Just runtimes
Rank 3: Container
yeah, that's strange
Rank 3: Container
% docker exec appwrite vars | grep _APP_EXECUTOR_RUNTIME_NETWORK
Rank 3: Container
even if .env contains only runtimes for network
Have you try running these?
Rank 3: Container
% docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
Good
No check these again
docker compose up -d
docker exec appwrite vars | grep _APP_EXECUTOR_RUNTIME_NETWORK
Is it working now?
Rank 3: Container
% docker exec appwrite vars | grep _APP_EXECUTOR_RUNTIME_NETWORK
Rank 3: Container
😦
So try reverse it at the end of docker-compose.yml
networks: gateway: name: gateway appwrite: name: appwrite runtimes:- name: runtimes+ name: appwrite-runtimesAnd restart the docker compose
Rank 3: Container
I just did docker prune and docker compose -d and reinit everything and now it looks like works...
Good
Rank 3: Container
But when I executed example function - An internal curl error has occurred within the executor! Error Msg: Operation timed out\nError Code: 500
Rank 3: Container
well...one more complete setup from scratch did the trick...still have no idea what was root cause