March 29, 20233 yr I recently joined Unraid and have been experiencing an issue where Docker is unable to access the Web UI in bridge mode. As the title suggests, I have had to continually run in host mode, but now some containers require the same port, so I still need to resolve this issue. Here are some details: 1. When I start a container in bridge mode, the command line display on the startup page shows WARNING: IPv4 forwarding is disabled. Networking will not work. According to the warning message, I have been searching for solutions and many of them suggest modifying the net.ipv4.ip_forward configuration item in the /etc/sysctl.conf file. However, this configuration item is already correct, and even after modifying it, it has no effect. 2. Using the sysctl net.ipv4.conf.all.forwarding=1 command temporarily solves the problem, but it becomes ineffective after a while, and I have to frequently execute this command in the console. 3. I tried to write this command into the /boot/config/go file for it to execute at startup, but it still did not take effect after rebooting. There is also an ongoing discussion on this issue on Reddit, link
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.