Docker Engine 20.10.17 error creating bridge endpoint

[Mordac85]

I had installed this updated pair before w/o any issues. But for various other reasons, I recently had to wipe and rebuild my NAS, an F5-221. The build kept giving me an error at 93% w/nothing I saw as an error on the monitor. Anyway, a reboot and it's all good it seems. OK, I setup my users, groups, volumes, permissions,etc w/o issue and everything seems fine. I installed ModBase & Cron_okm from new downloads then install Docker Engine and Docker Manager. I try to install portainer and then get an error.

Code: Select all

[me@NAS~]# docker run -d -p 8000:8000 -p 9443:9443 --name portainer --restart=always -v /var/run/docker.sock:/var/run/docker.sock -v portainer_data:/data portainer/portainer-ce:latest
b8141e4a7f8cebf8fc0ed803536082cc3c3de21955b7cf027f204023136fd76f
docker: Error response from daemon: failed to create endpoint portainer on network bridge: failed to add the host (vethce03081) <=> sandbox (veth2d56215) pair interfaces: operation not supported.

I tried everything to troubleshoot and resolve the issue w/o success. I was able to setup another container, but it used a host connection. So I forced portainer to a host connection using Docker Manager and it worked. As long as I don't use a bridge connection it works, even from the command line. I'm not sure if I have something going on w/my system or if this is an inherent problem w/the release in a net new environment. Any ideas would be appreciated b/c I can't continue to work this way.

[TMqiky]

May I ask if you have installed a third-party portainer that is currently being used in the application market?

[Mordac85]

No, I've never seen the point of installing portainer that way. I used the directions from Portainer.io Install Portainer CE with Docker on Linux. I just tried granting Allow to my normal user account that I use for most other containers under Control Panel > Privledges > Applications > Docker Engine, but that didn't resolve the issue with portainer.

[TMcola]

{L_BUTTON_AT}Mordac85

Here are some methods that can help you check it：
1.SSH to log in to the terminal and enter /sys to check if the kernel directory exists.
2.Use uname -r to view the system kernel version and use the command "docker info|grep Kernel" to check if the docker kernel version is consistent.
3.If they are not consistent, you need to reinstall the system and reload the kernel version.
4.If you still cannot start the container using bridge networking, you can delete the old image and pull a new image to try again.
5.If you have any other questions, please provide feedback in a timely manner.
Thanks!

[Mordac85]

Well, I guess I'm screwed. The kernel matches and I've tried pulling the images again. It's NOT the images. I'm in the process of restoring my data, so if I have to rebuild this thing again, please let me know.

Code: Select all

[me@NAS ~]# ls -l /sys
total 0
drwxr-xr-x   2 benjo benjo 0 Jan 31 11:27 block
drwxr-xr-x  27 benjo benjo 0 Jan 31 11:27 bus
drwxr-xr-x  72 benjo benjo 0 Jan 31 11:27 class
drwxr-xr-x   4 benjo benjo 0 Jan 31 11:27 dev
drwxr-xr-x  21 benjo benjo 0 Jan 31 11:27 devices
drwxr-xr-x   5 benjo benjo 0 Jan 31 17:45 firmware
drwxr-xr-x  13 benjo benjo 0 Jan 31 16:27 fs
drwxr-xr-x  14 benjo benjo 0 Jan 31 11:27 kernel
drwxr-xr-x 174 benjo benjo 0 Jan 31 11:27 module
drwxr-xr-x   3 benjo benjo 0 Feb  2 08:52 power

[benjo@Merlin ~]# uname -r
5.15.59

[me@NAS ~]# docker info|grep Kernel
WARNING: No blkio throttle.read_bps_device support
WARNING: No blkio throttle.write_bps_device support
WARNING: No blkio throttle.read_iops_device support
WARNING: No blkio throttle.write_iops_device support
 Kernel Version: 5.15.59

[Mordac85]

I just noticed the TNAS PC app doesn't detect my NAS. Do you think I have more system problems? Is there a link to a recommended method to wipe & rebuild my box?

[Mordac85]

That's version 5.0.35 from 2 different PCs, so I think it's the NAS.

[fethiye]

Thanks for information

[TMzethar]

Regarding the issue of TNAS PC not being able to find NAS, it is also possible that there is an issue with the PC or network settings. We suggest that you refer to this guide for troubleshooting:viewtopic.php?f=83&t=2250

[TMcola]

{L_BUTTON_AT}Mordac85

May I ask you a question? Have you used docker application of tos system very early? Maybe since tos 4? For your situation, it seems that the system lacks some kernel modules, such as veth. Generally, this problem can be solved by reinstalling the system. First, you can back up the current container data that is running. Then uninstall the docker manager and docker engine applications completely. Then you can refer to this link to reinstall the TOS system. viewtopic.php?f=76&t=423 There is no other way.