Docker Community Forums

Share and learn in the Docker community.

Process isolation does not allow port publishing with docker run...?

I try to use Docker Desktop 3.0.0 with Windows Containers and --isolation=process on Win10. It seems to me that the --publish does not work in that mode.
To test that, I created a small image with a service process that listens on port 8083, and returns a string with current time when connecting to that port (e.g. with curl)

Running in hyperv everything works fine:
docker run -d --publish 8083:8083 --isolation=hyperv e0e26f7f162d

I can do curl localhost:8083 on the host system and all works fine.

But with
docker run -d --publish 8083:8083 --isolation=process e0e26f7f162d
the container starts without errors, but the curl connect from the host times out. In fact, when I start a shell in the container and connect to localhost:8083 I get a response, so the service itself is running. Just the publishing (or forwarding) of the port to the host Windows system does not work.

Any idea what is missing?

Server: Docker Engine - Community
Engine:
Version: 20.10.0
API version: 1.41 (minimum version 1.24)
Go version: go1.13.15
Git commit: eeddea2
Built: Tue Dec 8 19:07:44 2020
OS/Arch: windows/amd64
Experimental: false

Microsoft Windows [Version 10.0.18363.1198]

Dockerfile:

FROM mcr.microsoft.com/windows/nanoserver:10.0.18363.1198
COPY TestServer.exe /
EXPOSE 8083
ENTRYPOINT [“TestServer.exe”]