Docker Engine 20.10.17 error creating bridge endpoint

[Mordac85]

Yes, I've been using Docker and your app since TOS 4; however, when I last rebuilt this ALL of the drives we're wiped and unallocated. But if there is any residual info it would be on the boot USB stick. Since I already went through the rebuild process mentioned in your link, is there a way to wipe the USB stick as well so I'm starting from a totally fresh install? I'm not sure if the factory reset would do that or if I'd really mess things up if I totally wiped the USB.

[Mordac85]

Alternatively, is there a way to get a list of the kernel modules I need and see if any are missing? Then it would at least be easier to add the modules than rebuilding the entire NAS.

[Mordac85]

fyi, it seems the UPnP discovery service has to be enabled for the TNAS PC app to detect a system. One irrelevant symptom resolved...

[Mordac85]

{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.

OK, well reinstalling TOS didn't fix the problem. The drives were wiped and fully synchronized before I did anything to the system but I still get failures trying to use the bridge network. Is there a way I can manually check the required files/modules?

[ColaChen]

{L_BUTTON_AT}Mordac85

It seems a bit difficult to determine the specific reason for this situation. Would it be convenient to arrange remote access and have our engineers check the details for you?

[jangoebel]

{L_BUTTON_AT}Mordac85

It seems a bit difficult to determine the specific reason for this situation. Would it be convenient to arrange remote access and have our engineers check the details for you?

Hi! Has this been resolved? I am getting the same error on F4-220 with 5.1. Kernel is 5.15.59, same for docker-kernel Freshly factory reset, version5, update, reboot, install docker from thread, reboot.

Code: Select all

Status: Downloaded newer image for hello-world:latest
docker: Error response from daemon: failed to create endpoint dreamy_montalcini on network bridge: failed to add the host (veth0c07b92) <=> sandbox (veth77e47fd) pair interfaces: operation not supported.
ERRO[0003] error waiting for container: context canceled 

[EthanLiu]

What version of the TOS system are you using? What is the application version of docker?

[jangoebel]

What version of the TOS system are you using? What is the application version of docker?

Hi!
Tos Version is 5.1(67-00214).
Docker (Engine) Version is: 20.10.17

[jangoebel]

@TMpraj @Mordac85 So is there a solution?

[EthanLiu]

Currently, we are unable to determine the specific reason for the issue. You may make an appointment for remote service through our official website, and we will arrange an engineer to remotely check your system. When making the appointment, please provide a screenshot of this forum post to the customer service personnel and describe your problem.