March 2, 20188 yr Hello, I am running 6.4.1-rc2 right now, and am having issues routing traffic from my unRAID server to the Docker containers that run on it. I have 4 VLANs setup on my network, with containers on each of them. All my containers are given unique IP addresses. This has been working great, and I can access all of these containers from anywhere except the unRAID server itself. The only reason I realized this is because I stopped using a VM for my DNS server and moved it to a container. After this, everything was still able to utilize the DNS server, except for the unRAID server. I'm sure I'm in the minority with all the VLANs, but even so, I'd think this should be possible. If anyone has experience, it'd be much appreciated.
March 3, 20188 yr First I recommend you upgrade to the official 6.4.1 release. With this release you create your VLANs without IP assignment (see network settings), this prevents unRAID participating directly. Next on the docker settings page (with docker stopped and advanced view) you set the network assignments for each VLAN you want to use for your docker containers. The above approach will allow a container to talk to the unRAID host system, but keep in mind that communication runs via your router and this device must ensure the proper routing.
March 3, 20188 yr Author @bonienl, thanks for the guidance! I did what you said, and I'm now on 6.4.1 official. I saw in settings how I no longer have to assign IP Addresses in the network settings (see picture below "network.png") As far as the docker settings, I'm a bit confused. Do I want to enable custom networks or no? My goal is to have all of these containers behave like mini-VMs and work through the router and only live on unRAID. (see picture below "docker.png") Thank you.
March 3, 20188 yr If you want to use VLAN 30 for your docker containers, you would need to enable it (br.30) under Docker settings and assign a network + gateway, optionally you can set a DHCP pool. E.g. address = 192.168.30.0/24, gateway = 192.168.30.1, DHCP pool = 192.168.30.128/25 The above will hand-out IP addresses 192.168.30.128 and up for containers with automatic assignments, or if you can specify a static IP address, use 192.168.30.2 up to .127 Do the same for VLAN 40, but use a different network, e.g. 192.168.40.0/24
March 4, 20188 yr Amazing.. I did not know the "none" drop down option existed in 6.4.1. Thank you so much for that! I can now drop use my own LE cert internally for unRAID thru the let's encrypt container. (don't worry only allowing access on internal subnets) I assume that is still in the 6.5rcs? Edited March 4, 20188 yr by smdion
Archived
This topic is now archived and is closed to further replies.