Complted Daily exercises Day 45, added comments Day 45

Days/day45.md

@@ -1,12 +1,13 @@
 ---
-title: '#90DaysOfDevOps - The anatomy of a Docker Image - Day 45'
+title: "#90DaysOfDevOps - The anatomy of a Docker Image - Day 45"
 published: false
 description: 90DaysOfDevOps - The anatomy of a Docker Image
-tags: 'DevOps, 90daysofdevops, learning'
+tags: "DevOps, 90daysofdevops, learning"
 cover_image: null
 canonical_url: null
 id: 1048777
 ---
+
 ## The anatomy of a Docker Image
 
 In the last session, we covered some basics of how we can use Docker Desktop combined with DockerHub to deploy and run some verified images. A recap on what an image is, you won't forget things if I keep mentioning them.
@@ -37,11 +38,11 @@ Together with a set of individual layer files, a Docker image also includes an a
 
 ### How to create a docker image
 
- There are two ways we can create a docker image. We can do it a little on the fly with the process that we started yesterday, we pick our base image spin up that container, and install all of the software and dependencies that we wish to have on our container. 
+There are two ways we can create a docker image. We can do it a little on the fly with the process that we started yesterday, we pick our base image spin up that container, and install all of the software and dependencies that we wish to have on our container.
 
- Then we can use the `docker commit container name` then we have a local copy of this image under docker images and in our docker desktop images tab. 
+Then we can use the `docker commit container name` then we have a local copy of this image under docker images and in our docker desktop images tab.
 
- Super simple, I would not recommend this method unless you want to understand the process, it is going to be very difficult to manage lifecycle management this way and a lot of manual configuration/reconfiguration. But it is the quickest and most simple way to build a docker image. Great for testing, troubleshooting, validating dependencies etc. 
+Super simple, I would not recommend this method unless you want to understand the process, it is going to be very difficult to manage lifecycle management this way and a lot of manual configuration/reconfiguration. But it is the quickest and most simple way to build a docker image. Great for testing, troubleshooting, validating dependencies etc.
 
 The way we intend to build our image is through a dockerfile. Which gives us a clean, compact and repeatable way to create our images. Much easier lifecycle management and easy integration into Continous Integration and Continuous delivery processes. But as you might gather it is a little more difficult than the first mentioned process.
 
@@ -116,3 +117,5 @@ Then if we go and take a look in our DockerHub repository you can see that we ju
 - [Docker documentation for building an image](https://docs.docker.com/develop/develop-images/dockerfile_best-practices/)
 
 See you on [Day 46](day46.md)
+
+# Completed exercises, Docker file

README.md

@@ -88,8 +88,8 @@ The quickest way to get in touch is going to be via Twitter, my handle is [@Mich
 
 - [✔️] 🏗️ 42 > [The Big Picture: Containers](Days/day42.md)
 - [✔️] 🏗️ 43 > [What is Docker & Getting installed](Days/day43.md)
-- [] 🏗️ 44 > [Docker Images & Hands-On with Docker Desktop](Days/day44.md)
+- [✔️] 🏗️ 44 > [Docker Images & Hands-On with Docker Desktop](Days/day44.md)
-- [] 🏗️ 45 > [The anatomy of a Docker Image](Days/day45.md)
+- [✔️] 🏗️ 45 > [The anatomy of a Docker Image](Days/day45.md)
 - [] 🏗️ 46 > [Docker Compose](Days/day46.md)
 - [] 🏗️ 47 > [Docker Networking & Security](Days/day47.md)
 - [] 🏗️ 48 > [Alternatives to Docker](Days/day48.md)