AdguardTeam / AdguardTeam/AdGuardHome
Docker Containers can connect to AdGuard GUI but Unable to Resolve via host IP
- Vorherrschende Sprache
- TypeScript
- Sterne
- 36.9k
- Forks
- 2.5k
- PR-Merge-Kennzahlen
- Keine gemergten PRs in 30 T.
Beschreibung
### Prerequisites
- [X] I have checked the [Wiki](https://github.com/AdguardTeam/AdGuardHome/wiki) and [Discussions](https://github.com/AdguardTeam/AdGuardHome/discussions/categories/q-a) and found no answer
- [X] I have searched other issues and found no duplicates
- [X] I want to report a bug and not [ask a question or ask for help](https://github.com/AdguardTeam/AdGuardHome/discussions/categories/q-a)
- [X] I have set up AdGuard Home correctly and [configured clients to use it](https://github.com/AdguardTeam/AdGuardHome/wiki/Clients). (Use the [Discussions](https://github.com/AdguardTeam/AdGuardHome/discussions/categories/q-a) for help with installing and configuring clients.)
### Platform (OS and CPU architecture)
Linux, AMD64 (aka x86_64)
### Installation
Docker
### Setup
On one machine
### AdGuard Home version
v0.107.41
### Action
Please bear with me on this. It's a confusing issue.
First of all, adguard docker-compose.yml:
```
version: "3.9"
services:
adguardhome:
image: adguard/adguardhome
container_name: adguardhome
ports:
- 53:53/tcp
- 53:53/udp
- 3000:3000/tcp
- 3001:80/tcp
- 3002:8902/tcp
volumes:
- ./conf:/opt/adguardhome/conf
- ./data:/opt/adguardhome/work
restart: always
network_mode: bridge
```
Pretty vanilla setup.
The host IP here is `192.168.25.81`.
```sh
user@192.168.25.81$ nslookup google.com 192.168.25.81
# now try to resolve from another docker container:
user@192.168.25.81:~/docker-configs/mosquitto$ docker compose exec mosquitto nslookup google.com 192.168.25.81
;; connection timed out; no servers could be reached
# however, the adguard container can still be reached on different ports.. why is that??
user@192.168.25.81:~/docker-configs/mosquitto$ docker compose exec mosquitto wget 192.168.25.81:3001 -O -
Connecting to 192.168.25.81:3001 (192.168.25.81:3001)
writing to stdout
Beitragsleitfaden
Bewertung
Dieses Issue wurde noch nicht bewertet.