Skip to content
This repository has been archived by the owner on Feb 22, 2023. It is now read-only.

DNS resolution problem #80

Open
g00g1 opened this issue Jul 14, 2022 · 1 comment
Open

DNS resolution problem #80

g00g1 opened this issue Jul 14, 2022 · 1 comment

Comments

@g00g1
Copy link

g00g1 commented Jul 14, 2022

Hello,
There is some issue with container IP addresses resolution:

db-standalone                        | 2022-07-14 10:51:40 1 [Warning] 'proxies_priv' entry '@ root@edc3d2ef0609' ignored in --skip-name-resolve mode.
db-standalone                        | 2022-07-14 10:51:40 1 [Note] Event Scheduler: Loaded 0 events
db-standalone                        | 2022-07-14 10:51:40 1 [Note] mysqld: ready for connections.
db-standalone                        | Version: '5.6.51'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  MySQL Community Server (GPL)
files-standalone                     | nc: bad address 'db'
files-standalone                     | waiting for db:3306...
syncing-server-js-standalone         | nc: bad address 'db'
syncing-server-js-standalone         | db:3306 is unavailable yet - waiting for it to start
auth-standalone                      | nc: bad address 'db'
auth-standalone                      | db:3306 is unavailable yet - waiting for it to start
syncing-server-js-worker-standalone  | nc: bad address 'db'
syncing-server-js-worker-standalone  | db:3306 is unavailable yet - waiting for it to start
api-gateway-standalone               | nc: bad address 'auth'
api-gateway-standalone               | auth:3000 is unavailable yet - waiting for it to start
auth-worker-standalone               | nc: bad address 'db'
auth-worker-standalone               | db:3306 is unavailable yet - waiting for it to start

Please help me troubleshoot this problem.

@mohammadrafigh
Copy link

same problem here

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants