I have the same issue. I was able to create a F: drive that was available in a running container with “VOLUME F:” in the dockerfile. However, I wasn’t able to actually do anything else with the volume in the dockerfile. For example, mkdir F:\somefolder in the dockerfile did not result in F:\somefolder existing in the running container. When I tried to COPY to F: in the dockerfile I got an error during build that docker for Windows only supports copying to the c:\ drive in the image. My workaround was to create the VOLUME F: in the dockerfile, copy to C: in the image, and set the ENTRYPOINT to a PowerShell script that did the F:\ drive operations at container run (e.g mkdir, copy from c: to f:, run processes that expect data on f:).