Network port occupied when using local windows volume share

I'm using docker desktop 2.1.0.4 for Windows
Docker version is 19.03.2
Version of Minecraft container is Docker 18.03.1-ee-3 on linux, amd64

I haven't an issue when trying to map a volume back to the local Windows computer where the container always says port is already in use.
E.g this command works fine
docker run -it -e EULA=TRUE -p 19139:19132/udp -v vol1:/data itzg/minecraft-bedrock-server

This command returns the error
docker run -it -e EULA=TRUE -p 19139:19132/udp -v c:/temp:/data itzg/minecraft-bedrock-server

DEBU[0000] Using /data to match uid and gid
DEBU[0000] Resolved UID=0 from match path
DEBU[0000] Resolved GID=0 from match path
DEBU[0000] Forwarding signal signal="window changed"
Starting Bedrock server...
NO LOG FILE! - setting up server logging...
[2019-10-23 14:31:05 INFO] Starting Server
[2019-10-23 14:31:05 INFO] Version 1.12.1.1
[2019-10-23 14:31:05 INFO] Session ID 5f68462a-8c40-4e67-91fd-e5d379eaf8fc
[2019-10-23 14:31:05 INFO] Level Name: Bedrock level
[2019-10-23 14:31:05 INFO] Game mode: 0 Survival
[2019-10-23 14:31:05 INFO] Difficulty: 1 EASY
[2019-10-23 14:31:05 ERROR] Network port occupied, can't start server.
Quit correctly

any idea of the issue, doesn't matter what internal port I try to map to always the same issue, I've also tried a prewritten server.prop file using different ports, this also produced the same error.

The issue names no files or tests. Start by reproducing the two docker run commands with the stated Windows bind mount and named volume, then compare the container logs and port configuration. Done means identifying the cause of the bind-mount-specific failure and documenting or implementing a verified resolution.

Written by the indexing model from the issue text.