Replies: 2 comments
-
|
First of all, sorry for the late reply. I just tested this once again and I do not see any such DNS resolving issue here with my default docker compose test environment. In fact, I can perfectly fire up the raspberrymatic docker container and the container is perfectly able to run In addition, the default And all this works with the default iptables setup within the container: So to me this looks like you might have a local misconfiguration in the docker host system which seem to prevent that the container is able to communicate with your local DNS system. Therefore I will move this ticket to the discussion part in case someone else might come up with a similar issue and you might to discuss things accordingl.y |
Beta Was this translation helpful? Give feedback.
-
|
Hello, no problem at all because of the late feedback, it works for me and so I am satisfied ;) The problem is probably related to the fact that I am running a pihole server for DNS resolution on the same system. If you are interested in the details, here is the pihole configuration:
FTLCONF_LOCAL_IPV4=192.168.145.5
TZ=Europe/Berlin
WEBPASSWORD=MySecretPassword
REV_SERVER=true
REV_SERVER_DOMAIN=fritz.box
REV_SERVER_TARGET=192.168.145.1
REV_SERVER_CIDR=192.168.145.0/24
HOSTNAME=pihole
DOMAIN_NAME=pihole.local
PIHOLE_WEBPORT=80
WEBTHEME=default-dark
services:
pihole:
container_name: pihole
image: cbcrowe/pihole-unbound:latest
hostname: ${HOSTNAME}
domainname: ${DOMAIN_NAME}
ports:
# - 443:443/tcp
- ${FTLCONF_LOCAL_IPV4}:53:53/tcp
- ${FTLCONF_LOCAL_IPV4}:53:53/udp
- ${FTLCONF_LOCAL_IPV4}:${PIHOLE_WEBPORT:-80}:80/tcp #Allows use of different port to access pihole web interface when other docker containers use port 80
# - 5335:5335/tcp # Uncomment to enable unbound access on local server
# - 22/tcp # Uncomment to enable SSH
environment:
- FTLCONF_LOCAL_IPV4=${FTLCONF_LOCAL_IPV4}
# - FTLCONF_REPLY_WHEN_BUSY=DROP
- TZ=${TZ:-UTC}
- WEBPASSWORD=${WEBPASSWORD}
- WEBTHEME=${WEBTHEME:-default-light}
- REV_SERVER=${REV_SERVER:-false}
- REV_SERVER_TARGET=${REV_SERVER_TARGET}
- REV_SERVER_DOMAIN=${REV_SERVER_DOMAIN}
- REV_SERVER_CIDR=${REV_SERVER_CIDR}
- PIHOLE_DNS_=127.0.0.1#5335
- DNSSEC="true"
- DNSMASQ_LISTENING=single
volumes:
- /home/skytale/docker/pihole:/etc/pihole:rw
- etc_pihole_dnsmasq-unbound:/etc/dnsmasq.d:rw
restart: unless-stopped
# dns: # https://github.com/pi-hole/docker-pi-hole/issues/342
# - 127.0.0.1
# - 8.8.8.8
volumes:
etc_pihole_dnsmasq-unbound: |
Beta Was this translation helpful? Give feedback.
-
Describe the issue you are experiencing
Hello everyone,
I have set up a raspberry latest distro with docker + raspberymatic and have problems with DNS resolution within the container.
I have created the container exactly according to the following blueprint: https://github.com/jens-maus/RaspberryMatic/wiki/Installation-Docker-OCI#using-docker-compose
The issue is now, that no DNS resolution is possible from within the container.
journalctlgives me the following messages cyclically:A CUxD script issuing a query fails and I have a alert inside raspberymatic web interface:
WatchDog: no-internet | ausgelöst | No internet connection detectedThrough an
nslookup wdr.defrom inside the container:and
journalctl:However, if I completely reset the
iptableswithin the container:The
nslookup wdr.deis now working from inside the container:/ # nslookup wdr.de Server: 127.0.0.11 Address: 127.0.0.11:53 Non-authoritative answer: Non-authoritative answer: Name: wdr.de Address: 149.219.209.51Also my CUxD script is now working.
I have reached the end of my knowledge, what am I doing wrong or how can I solve the
iptablesproblem properly and persistent? Thanks!Ps: I have now also played around a bit with the firewall settings within the web interface. Adding port
53does not help, only the optionports openis so far successful. I would like to see a proper solution, but in principle that would be fine with me. Isports opena security risk in a private LAN?Pss: Resolution is working after adding
try_exec_cmd "/usr/sbin/iptables -A INPUT -p udp --source-port 53 -j ACCEPT"tolibfirewall.tcland mapping it inside the container. That solution is however not very good, since I have to replace the complete file....Adding the port via web interface results in:
But what seems to be required is just this one rule:
Describe the behavior you expected
DNS requests should resolve
Steps to reproduce the issue
execinto the containernslookupanythingWhat is the version this bug report is based on?
3.75.7.20240420
Which base platform are you running?
rpi2 (RaspberryPi2, ARM/armhf)
Which HomeMatic/homematicIP radio module are you using?
n/a
Anything in the logs that might be useful for us?
May 11 13:32:07 homematic syslog.info syslogd started: BusyBox v1.36.1 May 11 13:32:10 homematic user.info firewall: configuration set May 11 13:32:44 homematic daemon.err xinetd[1044]: Unable to read included directory: /etc/config/xinetd.d [file=/etc/xinetd.conf] [line=14] May 11 13:32:44 homematic daemon.crit xinetd[1044]: 1044 {init_services} no services. Exiting... May 11 13:32:45 homematic daemon.info cuxd[1091]: CUx-Daemon(2.11) on CCU(3.75.7.20240420) start PID:1091 May 11 13:32:45 homematic daemon.info cuxd[1091]: write_pid /var/run/cuxd.pid [1091] May 11 13:32:45 homematic daemon.info cuxd[1091]: load paramsets(/usr/local/addons/cuxd/cuxd.ps) size:15 update(-62s):Sat May 11 13:31:43 2024 May 11 13:32:45 homematic daemon.info cuxd[1091]: 0 device-paramset(s) loaded ok! May 11 13:32:45 homematic daemon.info cuxd[1091]: write_proxy /var/cache/cuxd_proxy.ini (1091 /usr/local/addons/cuxd/ 2.11 3.75.7.20240420 0) May 11 13:32:45 homematic daemon.info cuxd[1091]: add interface 'CUxD' May 11 13:32:45 homematic user.info cuxd: started cux-daemon May 11 13:32:45 homematic daemon.info cuxd[1091]: write interface(1) 'VirtualDevices' to /usr/local/etc/config/InterfacesList.xml May 11 13:32:45 homematic daemon.info cuxd[1091]: write interface(2) 'CUxD' to /usr/local/etc/config/InterfacesList.xml May 11 13:33:01 homematic daemon.warn cuxd[1091]: process_rpc_request(127.0.0.1) - illegal XMLRPC(listDevices) request May 11 13:33:08 homematic daemon.warn cuxd[1091]: process_rpc_request(127.0.0.1) - illegal XMLRPC(init) request May 11 13:33:12 homematic daemon.info : starting pid 1277, tty '': '/bin/mv /tmp/boot.log /var/log/boot.log' May 11 13:33:12 homematic daemon.info : starting pid 1278, tty '/dev/null': '/usr/bin/monit -Ic /etc/monitrc' May 11 13:33:12 homematic user.info monit[1278]: Starting Monit 5.33.0 daemon with http interface at /var/run/monit.sock May 11 13:33:12 homematic user.info monit[1278]: 'homematic' Monit 5.33.0 started May 11 13:33:12 homematic local0.err ReGaHss: ERROR: SyntaxError: Error 1 at row 11 col 36 near ^(";", 1); } } Write(upl);^M [SyntaxError():iseESP.cpp:1149] May 11 13:33:12 homematic local0.err ReGaHss: ERROR: SyntaxError: (";", 1); } } Write(upl); [ParseProgram():iseESP.cpp:386] May 11 13:33:12 homematic local0.err ReGaHss: ERROR: SyntaxError: Error 1 at row 11 col 36 near ^(";", 1); } } Write(upl);^M [SyntaxError():iseESP.cpp:1149] May 11 13:33:12 homematic local0.err ReGaHss: ERROR: SyntaxError: (";", 1); } } Write(upl); [ParseProgram():iseESP.cpp:386] May 11 13:33:12 homematic local0.err ReGaHss: ERROR: SyntaxError: Error 1 at row 11 col 36 near ^(";", 1); } } Write(upl);^M [SyntaxError():iseESP.cpp:1149] May 11 13:33:12 homematic local0.err ReGaHss: ERROR: SyntaxError: (";", 1); } } Write(upl); [ParseProgram():iseESP.cpp:386] May 11 13:33:27 homematic user.err monit[1278]: 'sshdEnabled' status failed (1) -- no output May 11 13:33:27 homematic user.err monit[1278]: 'hs485dEnabled' status failed (2) -- grep: /var/etc/hs485d.conf: No such file or directory May 11 13:33:27 homematic user.err monit[1278]: 'multimacdEnabled' status failed (1) -- no output May 11 13:33:27 homematic user.err monit[1278]: 'hmlangwEnabled' status failed (1) -- no output May 11 13:33:27 homematic user.err monit[1278]: 'rfdEnabled' status failed (1) -- no output May 11 13:33:27 homematic user.warn monit[1278]: 'hasUSB' status failed (1) -- no output May 11 13:33:27 homematic user.err monit[1278]: 'hb_rf_eth-CheckEnabled' status failed (1) -- no output May 11 13:33:27 homematic user.err monit[1278]: 'coProcessorCheck' status failed (1) -- no output May 11 13:33:27 homematic user.warn monit[1278]: 'rpi4usb3Check' status failed (1) -- no output May 11 13:33:27 homematic user.err monit[1278]: 'tailscaleEnabled' status failed (1) -- no output May 11 13:33:27 homematic user.err monit[1278]: Lookup for '/media/usb1' filesystem failed -- not found in /proc/self/mounts May 11 13:33:27 homematic user.err monit[1278]: Filesystem '/media/usb1' not mounted May 11 13:33:27 homematic user.err monit[1278]: 'usb1' unable to read filesystem '/media/usb1' state May 11 13:33:27 homematic user.info monit[1278]: 'usb1' trying to restart May 11 13:33:28 homematic daemon.info cuxd[1091]: INIT 'xmlrpc_bin://127.0.0.1:31999' '1040' May 11 13:33:28 homematic daemon.info cuxd[1091]: RPC-server from HM-CCU (1040) registered! May 11 13:33:29 homematic daemon.info cuxd[1091]: connection to 127.0.0.1:8183 successfull! May 11 13:33:43 homematic user.warn monit[1278]: 'hasUSB' status failed (1) -- no output May 11 13:33:43 homematic user.warn monit[1278]: 'rpi4usb3Check' status failed (1) -- no output May 11 13:33:43 homematic user.err monit[1278]: Filesystem '/media/usb1' not mounted May 11 13:33:43 homematic user.err monit[1278]: 'usb1' unable to read filesystem '/media/usb1' state May 11 13:33:43 homematic user.info monit[1278]: 'usb1' trying to restart May 11 13:33:43 homematic user.warn monit[1278]: 'internetCheck' status failed (1) -- no output May 11 13:33:59 homematic user.warn monit[1278]: 'hasUSB' status failed (1) -- no output May 11 13:33:59 homematic user.err monit[1278]: 'rpi4usb3Check' status failed (1) -- no output May 11 13:33:59 homematic user.err monit[1278]: Filesystem '/media/usb1' not mounted May 11 13:33:59 homematic user.err monit[1278]: 'usb1' unable to read filesystem '/media/usb1' state May 11 13:33:59 homematic user.info monit[1278]: 'usb1' trying to restart May 11 13:33:59 homematic user.warn monit[1278]: 'internetCheck' status failed (1) -- no output May 11 13:34:15 homematic user.warn monit[1278]: 'hasUSB' status failed (1) -- no output May 11 13:34:15 homematic user.err monit[1278]: Filesystem '/media/usb1' not mounted May 11 13:34:15 homematic user.err monit[1278]: 'usb1' unable to read filesystem '/media/usb1' state May 11 13:34:15 homematic user.info monit[1278]: 'usb1' trying to restart May 11 13:34:15 homematic user.warn monit[1278]: 'internetCheck' status failed (1) -- no output May 11 13:34:31 homematic user.err monit[1278]: 'hasUSB' status failed (1) -- no output May 11 13:34:31 homematic user.warn monit[1278]: 'internetCheck' status failed (1) -- no output May 11 13:34:47 homematic user.warn monit[1278]: 'internetCheck' status failed (1) -- no output May 11 13:35:03 homematic user.warn monit[1278]: 'internetCheck' status failed (1) -- no output May 11 13:35:19 homematic user.warn monit[1278]: 'internetCheck' status failed (1) -- no output May 11 13:35:34 homematic user.warn monit[1278]: 'internetCheck' status failed (1) -- no output May 11 13:35:50 homematic user.warn monit[1278]: 'internetCheck' status failed (1) -- no output May 11 13:36:06 homematic user.warn monit[1278]: 'internetCheck' status failed (1) -- no output May 11 13:36:22 homematic user.warn monit[1278]: 'internetCheck' status failed (1) -- no output May 11 13:36:38 homematic user.warn monit[1278]: 'internetCheck' status failed (1) -- no output May 11 13:36:54 homematic user.warn monit[1278]: 'internetCheck' status failed (1) -- no output May 11 13:37:09 homematic user.warn monit[1278]: 'internetCheck' status failed (1) -- no output May 11 13:37:25 homematic user.warn monit[1278]: 'internetCheck' status failed (1) -- no output May 11 13:37:41 homematic user.warn monit[1278]: 'internetCheck' status failed (1) -- no output May 11 13:37:57 homematic user.warn monit[1278]: 'internetCheck' status failed (1) -- no output May 11 13:38:13 homematic user.warn monit[1278]: 'internetCheck' status failed (1) -- no output May 11 13:38:29 homematic user.warn monit[1278]: 'internetCheck' status failed (1) -- no output May 11 13:38:44 homematic user.warn monit[1278]: 'internetCheck' status failed (1) -- no output May 11 13:39:00 homematic user.warn monit[1278]: 'internetCheck' status failed (1) -- no output May 11 13:39:16 homematic user.warn monit[1278]: 'internetCheck' status failed (1) -- no output May 11 13:39:32 homematic user.warn monit[1278]: 'internetCheck' status failed (1) -- no output May 11 13:39:48 homematic user.err monit[1278]: 'internetCheck' status failed (1) -- no output May 11 13:39:48 homematic user.info monit[1278]: 'internetCheck' exec: '/bin/triggerAlarm.tcl No internet connection detected WatchDog: no-internet true' May 11 13:40:04 homematic user.err monit[1278]: 'internetCheck' status failed (1) -- no output May 11 13:40:20 homematic user.err monit[1278]: 'internetCheck' status failed (1) -- no output May 11 13:40:35 homematic user.err monit[1278]: 'internetCheck' status failed (1) -- no output May 11 13:40:51 homematic user.err monit[1278]: 'internetCheck' status failed (1) -- no output May 11 13:41:07 homematic user.err monit[1278]: 'internetCheck' status failed (1) -- no output May 11 13:41:23 homematic user.info monit[1278]: 'internetCheck' status succeeded (0) -- no outputAdditional information
For completeness, here is my network configuration:
nmcli device showBeta Was this translation helpful? Give feedback.
All reactions