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?

[TMcola]

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