This is a known issue for Docker for Windows on Windows 10 running a Windows container (i.e. nanoserver, not Ubuntu or any Linux OS). It would be most ideal to be able to copy into the container regardless of running/stopped in case user already has a separate session connection to triage an issue (don't want to kill that session). Unfortunately we can't, bummer, so perhaps we localize this only for Windows containers and explicitly check within the copy function before the copy - host OS and container (server daemon) OS and stop before copy and restart after. Bummer but probably necessary.
Also, this is lower priority issue; most testing is done on Linux OSes (and I have a VM of Nano running as well, so not a huge deal).
This is a known issue for Docker for Windows on Windows 10 running a Windows container (i.e. nanoserver, not Ubuntu or any Linux OS). It would be most ideal to be able to copy into the container regardless of running/stopped in case user already has a separate session connection to triage an issue (don't want to kill that session). Unfortunately we can't, bummer, so perhaps we localize this only for Windows containers and explicitly check within the copy function before the copy - host OS and container (server daemon) OS and stop before copy and restart after. Bummer but probably necessary.
Also, this is lower priority issue; most testing is done on Linux OSes (and I have a VM of Nano running as well, so not a huge deal).