Docker container is on custom network, using pihole as DNS server.
Using sites such as news.easynews.com fails as the docker container can not interact with DNS.
Tested with PING inside container and it is confirmed.
EDIT !!
Also just noticed it is not respecting the volumes and only seeing its internal directories.
Its like it is refusing to acknowledge the external network at all in any way.
Expected Behavior
NZB hosts should be able to resolve domain names using host DNS settings - these are set in both /etc/docker and daemon and inside the docker-compose.yml
Steps To Reproduce
Ubuntu in VM on Proxmox
docker-compose.yml
Caddy reverse_Proxy
Pihole DNS
Is there an existing issue for this?
Current Behavior
Docker container is on custom network, using pihole as DNS server.
Using sites such as news.easynews.com fails as the docker container can not interact with DNS.
Tested with PING inside container and it is confirmed.
EDIT !!
Also just noticed it is not respecting the volumes and only seeing its internal directories.
Its like it is refusing to acknowledge the external network at all in any way.
Expected Behavior
NZB hosts should be able to resolve domain names using host DNS settings - these are set in both /etc/docker and daemon and inside the docker-compose.yml
Steps To Reproduce
Ubuntu in VM on Proxmox docker-compose.yml Caddy reverse_Proxy Pihole DNS
Container is not accessing host DNS server.
Environment
CPU architecture
x86-64
Docker creation
Container logs