dependency failed to start: container twenty-server-1 is unhealthy
I'm trying to follow the 1-Click Docker Compose with a cloned repository. I'm on step 3 of launching the application, and then I'm hit with the twenty-server-1 is unhealthy
10 Replies
Here's a picture of the twenty-server-1 logs
Same thing also happens with this
Things I did:
- Copied
./packages/twenty-docker/twenty/Dockerfile to .
- Ran docker build . -t twenty:v1.0 to create a local image of the build
- Went to docker-compose.yml stored at . to replace all instances of twentycrm/twenty:${TAG} to twenty:v1.0 to use a local image instead of pulling from docker hub
- Ran docker-compose up -d at .
- Now works at localhost:3000
It's now displaying at localhost:3000, but the problem with 127.0.0.1:6379 still persists
Hi @Raphael , it seems like you don't have redis set up yet. There is the setup guides in step 4 of their document here https://twenty.com/developers/local-setup
Twenty - Local Setup
Mostly for contributors or curious developers
and make sure to update your env file with redis info
oh seems like 1-Click Docker Compose already set up redis but somehow your application couldn't detect the server, maybe you can check env file?
I am also having the same problem. I have used the manual installation for self-hosting. I tried on Portainer and Fresh install of Ubuntu with dependencies. Is there something else that needs to be done?
In the docker-compose file, add REDIS_HOST:redis to both server and worksr
Thank you Raphael, that worked. Is this a small bug then or did I miss it in the directions?
It's a small bug that the team's fixing. For more details you can check out this issue https://github.com/twentyhq/twenty/issues/7768
GitHub
When deploying the application in Docker (locally, on cloud Linux, ...
Bug Description When deploying the application in Docker (locally, on cloud Linux, or in Render), both the worker and server containers fail to connect to Redis, resulting in an ECONNREFUSED error....