floepie05

This is a gem of a remedy for those who want to have their cake and eat it. Hoping the devs can help route this tunnel via the new virtual interface if the setting 'host and docker networks communication' is enabled. This is very handy for DNS server containers, which should probably go via the host or in a macvlan or ipvlan network on the same host subnet. If you want to have HTTPS routed via your reverse proxy from within your LAN network and back out to the custom network, you will need host and custom network to communicate. This also allows the host to resolve the DNS server on the Br0.

After a looking a bit further, the setting "host access to custom networks" seems to create an additional network interface with the command as follows: ip link add shim-br0 link br0 type macvlan mode bridge ip link set shim-br0 up ip route add 192.168.1.0/25 dev shim-br0 ip route add 192.168.1.128/25 dev shim-br0 As such a route entry is created. It seems then the host is connected to two virtual interfaces, one bonded with br0 and the other bonded with shim-br0. This is probably why Chrome cries foul when a request is routed via a docker bridge network and then via the host (br0 and shim-br0 networks) to a container in the br0 network.

Hi, I have a container, namely Adguard-Home assigned to the Br0 (ipvlan) docker network. By default, this IP address on my LAN is not pingable from my unraid server, but is from any other device on my LAN. So, I have enabled the setting "host access to custom networks" in docker settings. Is this the same thing as promiscuous mode on the host's network interface? Anyway, this setting has allowed access to the ipvlan from the host. However, two strange issues still persist: 1. The console doesn't work from within the container - (docker exec -it appname sh) 2. Chrome gives a big warning the site is dangerous despite a valid cert. Any ideas why? Just trying figure out what's going on under the hood.

I suppose the title says it all. I'm trying to pinpoint which container is continually writing to cache. To narrow it down, I've disabled writing to log files within app settings, but the 'writes' keep climbing steadily.

Hi all, new-ish hardware is on the way! Just preparing for initial build. I have all new parts but would like to use the PSU from build with current HDs. The question is, will I be able to take new and empty HDs (2x), form an array, and mount two older NTFS drives from my Windows machine so that I copy them over to the array internally? Or, at least mount the NTFS drives as SMB shares, then copy over to array, then format old drives and add to array? (Just trying to avoid having to acquire an external HD enclosure). Thanks.