Docker wont load when firewall enabled

[pumalife]

Ive tried making every exception i can (adding child processes, exploring the various settings in each app exception), nothing works except disabling the tiny firewall entirely. Then when i start docker it will load, otherwise it fails

[colevr1]

I confirm the issue

[pumalife]

issue resolved. its a 'windows services' issue for docker. just add the docker service in tiny firewall and it works. its misleading because it wont show up in the tiny firewall 'show connections', so your just trial an error adding services that might be needed.

[PaszaVonPomiot]

just add the docker service in tiny firewall

You mean add process? What's exactly the name of it?

[YunseokChoi]

@pumalife Could you provide more information? I added 'Docker Desktop service' on exception list but no use. Put many other suspicious services on the list, but couldn't get Docker to run in the end.

It seems like 'Show connections' feature doesn't work for this. Docker is one of the industry standard software and I hope there is a solution.

[pumalife]

@pumalife Could you provide more information? I added 'Docker Desktop service' on exception list but no use. Put many other suspicious services on the list, but couldn't get Docker to run in the end.

It seems like 'Show connections' feature doesn't work for this. Docker is one of the industry standard software and I hope there is a solution.

@YunseokChoi @PaszaVonPomiot @colevr1
So I'll just list the various .exe ive added. Im not sure which one did it (prolly a combo)

C:\Program Files\Docker\Docker\resources\com.docker.backend.exe
C:\Program Files\Docker\Docker\resources\com.docker.build.exe
com.docker.service (C:\Program Files\Docker\Docker\com.docker.service); Type; Service
C:\Program Files\Docker\Docker\frontend\Docker Desktop.exe

most of them have 'no restrictions' and 'apply same rules for child processes' -whether that is important im not sure
the type service i added manually in the 'choose a service' button in the add firewall exception window

Hope it helps. Tiny firewall is great, but still needs some TLC polish

[YunseokChoi]

@pumalife I used the same exception settings, but Docker is still not running. I even added almost all exe files that belong to Docker to the exception list.

My Docker is running on WSL2. I have Tinywall checked for WSL2 on the Special Exceptions tab and Unblock LAN Traffic checked as well. Prevent modifications to hosts file is unchecked.

When I turn off Tinywall, Docker works fine... I'm not sure what to do anymore, but thanks for your response anyway.

[pylorak]

Please see #47.

[is-jonreeves]

I can confirm that the suggestion from @pumalife works for me on a Windows 11 Pro machine running Docker Desktop 4.35.0 (with WSL 2) and Tinywall 3.3.1.

I whitelisted the following Docker binaries with Unrestricted UDP and TCP traffic:

• com.docker.admin
• com.docker.build
• com.docker.dev-envs
• Docker Desktop.exe

I also had to set No restrictions to the following:

• WSLService (type Service)

Then the important requirement appears to be, that the following two require both Apply same rules to child processes and No restrictions:

• com.docker.backend
• com.docker.service (type Service)