![]() I'll publish, then build the images, and run it. This optimizes server density and resource. Be sure to read Steve Lasker's blog post " Building Optimized Docker Images with ASP.NET Core" to learn how to have one docker container build your app and the other run it it. Next, since I don't want Docker to do the building of my application yet, I'll publish it locally. ![]() FROM microsoft/aspnetcore:1.0.1ĮNTRYPOINT Starting from my ASP.NET Core app, I'll make sure my base image (that's the FROM in the Dockerfile) is the base ASP.NET Core image for Linux. Out of the box, I'm all setup to deploy my ASP.NET Core app to a Docker Linux container. This adds a basic Dockerfile and some docker-compose files. This menu comes from the Visual Studio Tools for Docker extension. Then I right click and Add | Docker Support. I'll say File | New Project and make a new ASP.NET Core application running on. I'll do everything from the command line or from Visual Studio. There's my Linux host that I don't really have to think about.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |