| 6 Sep 2025 |
 kraem | i just found out how to verify that it actually is mounted correctly:
systemd-cgls --unit wg-netns-test0 (lists pids running in the container) nsenter -a -t $pid cat /etc/resolv.conf (inside the nsenter) gives me the correct contents (which is different than my hosts)
so for some reason the processes inside the service isn't using the nameserver resolv.conf specified in the resolv.conf .. | 23:00:27 |
| kraem | do i need to run a separate resolver inside the service somehow, may | 23:01:57 |
| kraem | * do i need to run a separate resolver inside the service somehow? maybe the processes are calling into my hosts networkmanager resolver which is running with the hosts resolv.conf configuration? | 23:03:27 |
| kraem | i just found out how to verify that it actually is mounted correctly:
systemd-cgls --unit wg-netns-test0 (lists pids running in the container) nsenter -a -t $pid cat /etc/resolv.conf (inside the nsenter) gives me the correct contents (which is different than my hosts)
so for some reason the processes inside the service isn't using the nameserver specified in the resolv.conf .. | 23:05:20 |
| kraem | interesting. dig actually uses the bind mounted /etc/resolv.conf in the service but the python script i was testing with used my hosts nameserver.
i was using this script (https://gist.github.com/Tugzrida/6fe83682157ead89875a76d065874973) which uses socket.socket(socket.AF_INET, socket.SOCK_DGRAM), which should be using glibc if i understand correctly, which in turn makes it very strange because glibc should be reading the resolv.conf mounted inside the service? | 23:46:24 |
| 7 Sep 2025 |
 Jassuko | what does your nsswitch.conf look like? | 00:53:30 |
 hexa | https://www.servethehome.com/qnap-qsw-m3216r-8s8t-16-port-10gbe-managed-marvell-switch-review/ 🤔 | 01:02:15 |
| hexa | 8x10Gbase-T, 8xSFP+ | 01:02:31 |
| hexa | with fans, but apparently quiet | 01:02:46 |
| hexa | L2+ web-managed 🥲 | 01:03:00 |
| hexa | oh, per another listing this one actually has a console | 01:03:20 |
| hexa | what about ssh? 🤔 | 01:03:38 |
