My set up:
- Linux machine with hostname
remex-02running Gitea 1.20.2
- Windows machine running Docker Desktop v4.22.1
Both machines are correctly exposing their hostname and IP with mDNS.
When I try
docker login remex-02.local:3000
On the client I get
Authenticating with existing credentials... Login did not succeed, error: Error response from daemon: Get "https://remex-02.local:3000/v2/": dialing remex-02.local:3000 with direct connection: resolving host remex-02.local: lookup remex-02.local: getaddrinfow: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.
However the server logs indicate Docker did manage to connect:
Sep 2 10:13:04 remex-02 gitea: 2023/09/02 10:13:04 ...eb/routing/logger.go:102:func1() [I] router: completed GET /v2/ for [server-ipv6%wlan0]:52511, 401 Unauthorized in 0.2ms @ container/container.go:118(container.ReqContainerAccess) Sep 2 10:13:06 remex-02 gitea: 2023/09/02 10:13:06 ...eb/routing/logger.go:102:func1() [I] router: completed GET /v2/token?account=mark&client_id=docker&offline_token=true&service=container_registry for 10.0.0.50:52512, 200 OK in 1121.5ms @ container/container.go:142(container.Authenticate)
It’s as if at first DNS resolution is aware of mDNS, and later it isn’t. Has anyone experience with this set up? Any ideas if it possible at all, and if so how?