This article mainly describes how Visual Studio 2017 publishes Dotnet Core to Docker, which has some reference value, and interested partners can refer to
Docker benefits Needless to say, there is no understanding of the "Docker get Started", as a. NET veteran also want to catch the last bus to the Docker, reduce the various pits in the deployment. Following I was released after the release of Visual Studio 2017 (in fact VS2015 is also possible), completely run up the steps.
First step: install Docker
Download address: www.docker.com/docker-windows, download at the same time go to "Control Panel" "Program" to enable "hyper-V", the completion of the download is basically complete, to ensure that the download is complete, restart the computer, and then start to install Docker , the basic is "next" is finished.
Step two: preparing Docker
Local area network compatriots, need ladders, I use the SS, in Docker "settings", "proxies" fill in your agent, mine is "127.0.0.1:1080". No ladder to use the domestic mirror, in the "Settings", "daemon" filled with photographed like address:/HTTP F2d6cb40.m.daocloud.io (Mirror This I have not tested, I use a ladder, on the internet also said that this matching agent can not be used, I do not know whether it is not his SS "led from the local area network link" caused by, my configuration is ready to use). Then enable disk sharing. "Settings", "shared drives" must enable the C drive, (to be exact, the system disk), and then enable the disk where the project is located. All operations
Step Three: open vs2017 to create a new Dotnetcore Web project, notice the Docker support, and, of course, you can right-click Add-Docker support in the Solution Explorer project. (The red box is the necessary file for Docker) and this time it can be F5 in Docker mode.
Operation effect: can be seen in docker-"kitematic". Of course, the host browser will also see.
OK, there will be no ladder in the case of N-pit, and the hint is very strange!