Thank You for Choosing to Learn from in28Minutes

Author: Ranga Karanam

_posts/2020-03-14-Docker.md

@@ -47,7 +47,6 @@ Are you ready to jump into the world of Docker?
 Docker is popular because of the possibilites it opens for software delivery and deployment. Many common problems and inefficiences are resolved with containers.
 
 The awesome thing about Docker is, you can easily install Docker on Cloud. Most of the cloud providers provide container based services
-![alt text](https://github.com/in28minutes/docker-course-with-java-and-spring-boot-articles/blob/master/section02-getting-started-with-docker/resources/02-getting-started-with-docker-step06-001.png)
 
 They provide services where you just need to provide a docker Image and it would automatically run on the cloud.
 
@@ -56,13 +55,13 @@ They provide services where you just need to provide a docker Image and it would
 Before Docker, virutal machines were very popular.
 
 The image below shows the typical architecture with a Virtual Machine
-![alt text](https://github.com/in28minutes/docker-course-with-java-and-spring-boot-articles/blob/master/section02-getting-started-with-docker/resources/02-getting-started-with-docker-step06-002.png)
+![alt text](images/vm-architecture.png)
 
 As you can see there are two operating systems present one is Guest OS and another is Host OS.
 
 Due to this, virutal machine architecture becomes heavyweight. Hence you will not be able to benefit from the entire power of your hardware because of virutalization.
 
-![alt text](https://github.com/in28minutes/docker-course-with-java-and-spring-boot-articles/blob/master/section02-getting-started-with-docker/resources/02-getting-started-with-docker-step06-003.png)
+![alt text](images/docker-vs-VM-02.png)
 
 With Docker, all that you need to run containers is a Docker Engine. Other main reasons why Docker is popular is:
 
@@ -88,7 +87,7 @@ The rise of microservice architecture also one of the reason for Docker populari
 
 Docker uses a client-server architecture. The Docker client talks to the Docker `daemon`, which does the heavy lifting of building, running, and distributing your Docker containers. The Docker client and daemon can run on the same system, or you can connect a Docker client to a remote Docker daemon. The Docker client and daemon communicate using a REST API, over UNIX sockets or a network interface. 
 
-![Docker Architecture](https://github.com/in28minutes/docker-course-with-java-and-spring-boot-articles/blob/master/section02-getting-started-with-docker/resources/02-getting-started-with-docker-step05-001.png)
+![Docker Architecture](images/docker-architecture.png)
 
 #### Docker daemon
 
@@ -142,7 +141,7 @@ You can clone or download the entire github repository and import this project a
 
 Here is the screenshot of the project setup in Eclipse.
 
-![alt text](https://github.com/in28minutes/docker-course-with-java-and-spring-boot-articles/blob/master/section04-containerizing-java-spring-boot-hello-world-rest-api-with-docker/resources/04-containerizing-java-spring-boot-hello-world-rest-api-step01-001.png)
+![alt text](images/04-containerizing-java-spring-boot-hello-world-rest-api-step01-001.png)
 
 If you are new to Spring and Spring Boot, you can watch these - [Spring in 10 Steps](https://courses.in28minutes.com/p/spring-framework-for-beginners) and [Spring Boot in 10 Steps](https://courses.in28minutes.com/p/spring-boot-for-beginners-in-10-steps) to understand how Spring and Spring Boot work together.
 
@@ -174,8 +173,8 @@ Building a JAR file should be really easy. All that you need to is do a clean Ma
 
 This would compile the code, run the unit tests, and finally, a JAR would be packaged. 
 
-![image info](https://github.com/in28minutes/docker-course-with-java-and-spring-boot-articles/blob/master/section04-containerizing-java-spring-boot-hello-world-rest-api-with-docker/resources/04-containerizing-java-spring-boot-hello-world-rest-api-step02-003.png)
-![image info](https://github.com/in28minutes/docker-course-with-java-and-spring-boot-articles/blob/master/section04-containerizing-java-spring-boot-hello-world-rest-api-with-docker/resources/04-containerizing-java-spring-boot-hello-world-rest-api-step02-004.png)
+![image info](images/04-containerizing-java-spring-boot-hello-world-rest-api-step02-003.png)
+![image info](images/04-containerizing-java-spring-boot-hello-world-rest-api-step02-004.png)
 
 The name of the JAR is ```hello-world-rest-api.jar```, and it is under the ```target``` folder. 
 
@@ -215,7 +214,7 @@ Let's now run the alpine jdk image.
 ```openjdk:8-jdk-alpine``` image will be dowloaded from Docker Hub. It would take a little while as it is a large - ```100 MB``` download. 
 
 You can run `docker images` to see the downloaded image.
-![alt text](https://github.com/in28minutes/docker-course-with-java-and-spring-boot-articles/blob/master/section04-containerizing-java-spring-boot-hello-world-rest-api-with-docker/resources/04-containerizing-java-spring-boot-hello-world-rest-api-step02-007.png)
+![alt text](images/04-containerizing-java-spring-boot-hello-world-rest-api-step02-007.png)
 
 Run ```docker container ls``` to see the running container -  ```naughty_knuth```. 
 
@@ -228,9 +227,9 @@ The third step is to copy the JAR into the specific image. Then, we would want t
 Here's the command to copy a jar file into the container:
 
 `docker container cp target/hello-world-rest-api.jar naughty_knuth:/tmp`
-![image info](https://github.com/in28minutes/docker-course-with-java-and-spring-boot-articles/blob/master/section04-containerizing-java-spring-boot-hello-world-rest-api-with-docker/resources/04-containerizing-java-spring-boot-hello-world-rest-api-step02-008.png)
-![image info](https://github.com/in28minutes/docker-course-with-java-and-spring-boot-articles/blob/master/section04-containerizing-java-spring-boot-hello-world-rest-api-with-docker/resources/04-containerizing-java-spring-boot-hello-world-rest-api-step02-009.png)
-![image info](https://github.com/in28minutes/docker-course-with-java-and-spring-boot-articles/blob/master/section04-containerizing-java-spring-boot-hello-world-rest-api-with-docker/resources/04-containerizing-java-spring-boot-hello-world-rest-api-step02-010.png)
+![image info](images/04-containerizing-java-spring-boot-hello-world-rest-api-step02-008.png)
+![image info](images/04-containerizing-java-spring-boot-hello-world-rest-api-step02-009.png)
+![image info](images/04-containerizing-java-spring-boot-hello-world-rest-api-step02-010.png)
 
 You can also use the ID of the container. 
 
@@ -285,7 +284,7 @@ How can we do that?
 
 We are adding a startup command by using an option ```--change```. 
 
-![image info](https://github.com/in28minutes/docker-course-with-java-and-spring-boot-articles/blob/master/section04-containerizing-java-spring-boot-hello-world-rest-api-with-docker/resources/04-containerizing-java-spring-boot-hello-world-rest-api-step02-011.png)
+![image info](images/04-containerizing-java-spring-boot-hello-world-rest-api-step02-011.png)
 
 #### Running The Container Again
 
@@ -295,11 +294,11 @@ Let's do ```docker images```, and a new image is seen to be created with tag as
 
 > If you have any container running on 8080, you can stop it.
 
-![image info](https://github.com/in28minutes/docker-course-with-java-and-spring-boot-articles/blob/master/section04-containerizing-java-spring-boot-hello-world-rest-api-with-docker/resources/04-containerizing-java-spring-boot-hello-world-rest-api-step02-013.png)
+![image info](images/04-containerizing-java-spring-boot-hello-world-rest-api-step02-013.png)
 
 If we go to the browser and refresh, the URL continues to work. 
 
-![image info](https://github.com/in28minutes/docker-course-with-java-and-spring-boot-articles/blob/master/section04-containerizing-java-spring-boot-hello-world-rest-api-with-docker/resources/04-containerizing-java-spring-boot-hello-world-rest-api-step02-014.png)
+![image info](images/04-containerizing-java-spring-boot-hello-world-rest-api-step02-014.png)
 
 This image we can share with anyone in the world and they can run in all environment they would wish to.