VisibleStea1th

Is the issue that you have containers talking to one another using the internal docker network and you have them referencing each other based on the docker IP? I believe the fixed IP, which shows up for me when i choose a custom bridge, is only used when you are giving the container an IP on you LAN and is not used as a way to set the internal docker IP for that container. Are you familiar with Portainer? If so, I would try setting a container specific IP in the network settings for that particular container.

I am having an issue increasing the maximum number of open files. When i start my influxdb container, the logs for that container show scrolling errors about too many files open. This cascades into other docker containers also showing this in their log. I lose user shares and overall things just grind to a halt. Reading online, it appears that the nofile limit needs to be changed in three places. I need help with changing it at the docker daemon level. The Host Done manually using the Unraid CLI and executing "ulimit -n 256000" Can also be added to a user script to execute when the array starts but i haven't tested this yet Docker container that needs it. Added to extra parameters "--ulimit nofile=80000:80000" The Docker Daemon Based on the output of the command below, the daemon is set to 40960 cat /proc/$(ps -A | grep dockerd | awk '{print $1}')/limits | grep "files" I Have only found a way to change this in a more traditional implementation of Docker. cat /etc/init.d/docker | grep ulimit ulimit -n 256000