Jaymoulin/JDownloader on Docker Rpi4
-
-
I tried also with the command from Soma again: "
docker exec -it jdownloader sh"
Codepi@raspberrypi:~ $ sudo docker exec -it JDownloader sh /opt/JDownloader $ ping -c 5 google.com ping: bad address 'google.com' /opt/JDownloader $ ping -c 5 8.8.8.8 PING 8.8.8.8 (8.8.8.8): 56 data bytes ping: permission denied (are you root?) /opt/JDownloader $ ping update.appwork.org ping: bad address 'update.appwork.org' /opt/JDownloader $
-
So it seems pretty clear the container is not able to connect. Is this due to missing rights?
-
-
Your name resolution is strange, normally the docker containers use the DNS resolution on the host. In your case the hos name resolution works, but not insided the container. Have you done any special settings?
- macvalan with dhcp
- DNS resolver inside the container
-
none I'm aware off.
Could the pihole affect some wired stuff ?
-
Try to shut it down and see.
-
-
Does not help.
Any other ideas?
-
check if nslookup or dig are installed inside the container.
If not, cat /etc/resolv.conf from inside the container.
-
ok I'm now pretty sure its a DNS problem
pi@raspberrypi:~ $ sudo docker exec -u 0 -it JDownloader sh
/opt/JDownloader # ping -c 5 google.com
ping: bad address 'google.com'
/opt/JDownloader # ping -c 5 8.8.8.8
PING 8.8.8.8 (8.8.8.8): 56 data bytes
64 bytes from 8.8.8.8: seq=0 ttl=116 time=15.025 ms
64 bytes from 8.8.8.8: seq=1 ttl=116 time=15.419 ms
64 bytes from 8.8.8.8: seq=2 ttl=116 time=11.278 ms
64 bytes from 8.8.8.8: seq=3 ttl=116 time=12.137 ms
64 bytes from 8.8.8.8: seq=4 ttl=116 time=11.656 ms
--- 8.8.8.8 ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 11.278/13.103/15.419 ms
/opt/JDownloader #
I need to check how I can solve this.
I just need to understand how it works for different containers. In Portainer I can see that the Pihole is under the Network "bridge". The big question would be, how can I grant access to the internet also to the other containers.
-
-
It is not a network problem, as you can ping the google name server 8.8.8.8.
cat /etc/resolv.conf inside the container will show how it is trying to resolve dns names.
-
Gentlemen,
I solved it!
The issue was Pi-Hole. I deactivated it completely and did reset the DNS server in my fritz.box.
Before I did that I noticed that the pihole is receiving the requests for update.appwork.org was resolving the DNS is request but was apparently not returning the "IP answer" to the right container.
I need now to understand - How to I manage that every container is receiving their DNS answer again.
-
If this name on a block list?
-
-
no all entries have passed and been responded by pi-hole with the respective server IP.
I think its just about to be rturned to the right container...How does this work?
How does each container know..."yes this was my DNS request I take the responded IP adress"
-
Just a thought:
Are you setting your whole LAN to use the Pi-Hole DNS?
-
so I changed the DNS Server inside my fritz box to the IP address of the pihole.
So no matter which channel lan / wlan the DNS Server is always my pihole.
And I gave the pihole a static local IP address inside my network.
-
-
Quick solution.
In portainer I added a dedicated DNS to the container.
That solves it. So just this container is not using pihole.
Thanks and can be closed.
Participate now!
Don’t have an account yet? Register yourself now and be a part of our community!