Replies: 1 comment
-
Hey @cauduan, For the database error (FATAL: role "root" does not exist), it usually means that the PostgreSQL container is expecting a specific database user to be created on startup, but that user hasn’t been defined in your Docker environment variables (like POSTGRES_USER). Make sure your docker-compose.yml or .env file includes the correct user and password settings for the database, and that the Django app is configured to use them. The OperationalError and "No route to host" log from the Celery Beat container likely means it can’t connect to the database—either because the database container isn't running properly, or the network configuration between the services is misconfigured. Once the DB issue is fixed, this should resolve itself. For the time zone difference: environment:
- TZ=Asia/Shanghai # Or your desired timezone Or mount the timezone files: volumes:
- /etc/timezone:/etc/timezone:ro
- /etc/localtime:/etc/localtime:ro To help you better, could you share your docker-compose.yml, .env file (remove sensitive data), and the full logs you’re seeing? Let’s troubleshoot it together! |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I would like to ask two additional questions:
Is the server running on that host and accepting TCP/IP connections?
Beta Was this translation helpful? Give feedback.
All reactions