Download as PDF, PPTX
![Dockerfile
FROM microsoft/dotnet:2.1-aspnetcore-
runtime
WORKDIR /app
COPY output/app .
ENTRYPOINT ["dotnet", "HelloWorld.dll"]
FROM microsoft/dotnet:2.1-aspnetcore-runtime AS base
WORKDIR /app
EXPOSE 80
FROM microsoft/dotnet:2.1-sdk AS build
WORKDIR /src
COPY ["HelloWorld/HelloWorld.csproj", "HelloWorld/"]
RUN dotnet restore "HelloWorld/HelloWorld.csproj"
COPY . .
WORKDIR "/src/HelloWorld"
RUN dotnet build "HelloWorld.csproj" -c Release -o /app
FROM build AS publish
RUN dotnet publish "HelloWorld.csproj" -c Release -o /app
FROM base AS final
WORKDIR /app
COPY --from=publish /app .
ENTRYPOINT ["dotnet", "HelloWorld.dll"]](https://image.slidesharecdn.com/devopsfusion2019-dockerwhythefuturetakesplaceincontainers-190703042946/85/DevOps-Fusion-2019-Docker-Why-the-future-takes-place-in-containers-20-320.jpg)
Uploaded byMarc Müller
DevOps Fusion 2019: Docker - Why the future takes place in containers
The document is a presentation by Marc Müller on the benefits of using Docker containers in software development and deployment. It covers key concepts such as container basics, building Docker containers, DevOps workflows, and the importance of versioned artifacts. The presentation emphasizes the advantages of containers, including isolation, fast deployment, and ease of orchestration.
More Related Content
Similar to DevOps Fusion 2019: Docker - Why the future takes place in containers
DevOps Fusion 2019: Docker - Why the future takes place in containers
- 1. MarcMüller PrincipalConsultant marc.mueller@4tecture.ch @muellermarc www.4tecture.ch DOCKER - WHYTHE FUTURE TAKES PLACE IN CONTAINERS
- 2.
- 3. Agenda Intro Container Basics Build aDocker Container Docker for CLI Docker in DevOps Workflows
- 4.
- 5. Write Code Customer usethe code Write Code Customer use the code
- 6.
- 7. Automated deployment Infrastructure asCode Versioned Artifacts Staged Environments
- 8. Artifact Challenges ▪ Versioned ▪Immutable ▪ No «dependency hell» ▪ Runs everywhere ▪ Minimalistic setup on target machine ▪ Fast ▪ Easy to test, no more «no repro»
- 9.
- 10.
- 11. Containers ▪ Versioned artifact ▪Isolated deployable unit ▪ Container image is bit by bit identical when deployed ▪ Abstraction of data center resources ▪ Pool of compute, network and storage ▪ Orchestration is “Cattle Business” ▪ “Forget about naming the servers and treating them like pets.” ▪ “Run it for me please”
- 12.
- 13. Demo Hello World WebApplication with Docker
- 15. Server Host OS Hypervisor Server Host OS DockerEngine Guest OS Guest OS Guest OS Bins/Libs Bins/Libs App A App A’ App B Bins/Libs Bins/Libs AppA AppA’ AppB AppB’ AppB AppB’ AppB AppB’ Containers are isolated, but share OS and, where appropriate, bins/librariesBins/Libs Image Source: https://sec.ch9.ms/sessions/build/2016/B822.pptx
- 16. My ASP.NET CoreApplication microsoft/dotnet:2.1.4- aspnetcore-runtime microsoft/dotnet:2.1-runtime- deps-alpine3.7 alpine:3.7
- 17. File System Layers ▪Rootfs stays read-only ▪ Union-mount file system over the read-only file system ▪ Multiple file systems stacked on top of each other ▪ Only top-most file system is writable ▪ Copy-on-write
- 20. Dockerfile FROM microsoft/dotnet:2.1-aspnetcore- runtime WORKDIR /app COPYoutput/app . ENTRYPOINT ["dotnet", "HelloWorld.dll"] FROM microsoft/dotnet:2.1-aspnetcore-runtime AS base WORKDIR /app EXPOSE 80 FROM microsoft/dotnet:2.1-sdk AS build WORKDIR /src COPY ["HelloWorld/HelloWorld.csproj", "HelloWorld/"] RUN dotnet restore "HelloWorld/HelloWorld.csproj" COPY . . WORKDIR "/src/HelloWorld" RUN dotnet build "HelloWorld.csproj" -c Release -o /app FROM build AS publish RUN dotnet publish "HelloWorld.csproj" -c Release -o /app FROM base AS final WORKDIR /app COPY --from=publish /app . ENTRYPOINT ["dotnet", "HelloWorld.dll"]
- 21. Build a ContainerImage Create the image based on Dockerfile docker build –t <reponame>:<tag> . List the images docker image ls REPOSITORY TAG IMAGE ID HelloWorld latest 326387cea398
- 22. Definitions ▪ Container A containerdefines a software application and its dependencies wrapped in a complete filesystem including code, runtime, system tools, and libraries. ▪ Image An image is a read-only snapshot of a Docker container.
- 23. Where to storethe images? ▪ Docker Hub ▪ Azure Container Registry ▪ …
- 24. Developer PC /Laptop Environments - Development Docker Engine Container Container Container
- 25. Environments – Hosting/ Cloud
- 26.
- 27. AKS CI /CD Azure DevOps Build Azure DevOps Release Docker Registry Build App Test Build Container Repo Helm Upgrade Publish to Target AKS (Cluster) Helm Chart (Config) Push Host / Cluster Pull Config Artifact
- 28. Short recap ▪ Bitby bit images ▪ Fast deployment / fast startup ▪ Simple scaling and partitioning ▪ Isolated, versioned, reusable code (artifact / configuration element) Clear distinction between development and operations ▪ Dev takes care of the contents of the container ▪ Ops takes care of the operations of the container
- 29.
- 30. Use Docker forCLI Tooling Tools installation can pollute the system. Why not using Docker Containers on the CLI?
- 31.
- 33. Azure Cloud Shell ImageSource: https://docs.microsoft.com/en-us/azure/cloud-shell/overview
- 34.
- 35. Recap Container – aperfect artifact ▪ Bit by bit images ▪ Simple scaling and partitioning ▪ Isolated, versioned, reusable code (artifact / configuration element) Fast and low footprint ▪ Fast deployment ▪ Fast startup ▪ Ease of deployment Orchestration ▪ Enterprise Grade Hosting Environments ▪ Simple Scaling and Failover ▪ Abstraction at Container Level
- 36. Thank you foryour attention! If you have any questions do not hesitate to contact us: 4tecture GmbH Marc Müller Aathalstrasse 84 Principal Consultant CH-8610 Uster +41 44 508 37 00 marc.mueller@4tecture.ch info@4tecture.ch @muellermarc www.4tecture.ch
- 37.
- 38. We are lookingfor great talents to join our team! Apply to job@4tecture.ch www.4tecture.ch/jobs