adamfritzsche

Any further ideas on why this is happening?

Right. That is how I had it for years, no issue. All of a sudden dockers will not communicate with each other using the Host IP and I fail to understand why. I can and do access these dockers via the host ip and corresponding port from anywhere else, except another docker. This was my previous setup, which no longer works. Now to get them to work I have to use this, which is problematic.

Yes, most of them are using bridge.

Any other advice on this? It is rather frustrating. Using the 172.* subnet works, but the ip's for the dockers on this subnet are not static, so I am constantly having breaks in the communication between dockers and have to go into them and change the ip's around when they end up changing at random.

A few months ago out of the blue my docker containers were unable to communicate between each other using the local subnet I am using (192.168.1.0/24). I can reach them via any other device on the subnet no problem. After a large struggle, I found that they will communicate via the docker subnet? (172.17.0.XXX). This provided an immediate solution but not an answer to what happened as I have had this setup for several years without issue. The issue using the docker subnet (or whatever it is actually referred to) is that the IP changes randomly and then I have to go through a bunch of dockers to reflect these changes. Any ideas to a solution, one way or another?

I had rebooted the server prior to pulling these diags. It looks like the logs start then and it did start docker, so it looks like the logs don't show the time of the incident. unraidserver-diagnostics-20200524-0801.zip

The last couple days I have been having issues with docker stopping at exactly the same time every morning and then not coming back up. I looked at the logs and realized that was when CA Backup does a backup of my appdata folder and then I see the error that /mnt/cache/docker.img is in-use, cannot mount. I then spend the next 30 minutes trying to get docker to start again, which includes some restarts of the machine, stopping and starting Docker until it just finally starts up. I have disabled these auto backups for now to hopefully alleviate the issue temporarily, but I am just curious to know why this all of a sudden started happening and wondering if anyone has any ideas. I have been doing these backups for at least the last year no issues and it does not look like anything has been updated in the last couple days to change behavior.

Ah, yes. That makes sense. Thank you.

Okay, so I have a dumb question. I have pfSense as a VM in unRaid. I have a quad Intel nic passed through to the VM. Port Designated WAN goes to cable modem, LAN goes to switch, which then goes to all my wired devices and wireless AP's. One of these ports on the switch goes back to the unRaid server onboard nic, which is used to give unRaid network access. This all works great until I restart the unRaid Machine. Obviously, unRaid starts before the pfSense VM can, resulting in the unRaid machine getting assigned a 169.xxx.xxx.xxx address which then results in not being able to access unRaid, have to put the old router back in place to get access again. Am I missing something? / Is there a way to resolve this?

Syncthing is pretty good. That is what I was using when I was still using Open Media Vault. I think BTSync is another one, but I could not getting it working on OMV, and I was disappointed because I wanted to use that over Syncthing for some reason, but have no clue what that was now.

What I did was installed OpenVPN and started setting it up, but had to go to work before I had everything the way I wanted, so I stopped the OpenVPN Docker. When I did this, the webUI stopped responding immediately.

Awesome. Thanks for the insight. I do plan on maxing my ram out (16GB). There looks to be some options in the bios for ECC, so I need to see if my mobo does infact support ECC before my RAM purchase. I think my processor (AMD Phenom II X3) supports unbuffered unregistered ECC.

4gb. It looked like it was only using about 30% when it crashed. I was playing around setting up OpenVPN docker and I when to stop the docker and that is when it crashed. What is the proper restart method once the preclear that is still going done?

So I just moved over from Open Media Vault, I transferred all my data over to other disks in the array, so I could take my 3TB HD and make it the Parity Drive. I am doing the preclear on the drive (preclear script and accompanying plugin). I am about 18 hours in and the web gui crashed. All of my dockers are still active and from what I can tell from HD activity, the preclear is still going. What do I do at this point? Is there a way to restart the web gui? I found a few posts about killing a restarting emhttp, but have also read that this does not work in current versions and that a restart is necessary? Is there a way to see the progess of the preclear via terminal? If I have to restart, I would much rather wait until the preclear is done. Any help would be greatly appreciated.