Spelling & Grammar Day 47

Days/day47.md

@@ -9,23 +9,23 @@ id: 1049078
 ---
 ## Docker Networking & Security
 
-During this container session so far we have made things happen but we have not really looked at how things have worked behind the scenes either from a networking point of view but also we have not touched on security, that is the plan for this session. 
+During this container session so far we have made things happen but we have not looked at how things have worked behind the scenes either from a networking point of view also we have not touched on security, that is the plan for this session. 
 
 ### Docker Networking Basics 
 
 Open a terminal, and type the command `docker network` this is the main command for configuring and managing container networks. 
 
-From the below you can see this is how we can use the command, and all of the sub commands available. We can create new networks, list existing, inspect and remove networks. 
+From the below, you can see this is how we can use the command, and all of the sub-commands available. We can create new networks, list existing ones, and inspect and remove networks. 
 
 ![](Images/Day47_Containers1.png)
 
-Lets take a look at the existing networks we have since our installation, so the out of box Docker networking looks like using the `docker network list` command. 
+Let's take a look at the existing networks we have since our installation, so the out-of-box Docker networking looks like using the `docker network list` command. 
 
 Each network gets a unique ID and NAME. Each network is also associated with a single driver. Notice that the "bridge" network and the "host" network have the same name as their respective drivers.
 
 ![](Images/Day47_Containers2.png)
 
-Next we can take a deeper look into our networks with the `docker network inspect` command. 
+Next, we can take a deeper look into our networks with the `docker network inspect` command. 
 
 With me running `docker network inspect bridge` I can get all the configuration details of that specific network name. This includes name, ID, drivers, connected containers and as you can see quite a lot more. 
 
@@ -33,7 +33,7 @@ With me running `docker network inspect bridge` I can get all the configuration
 
 ### Docker: Bridge Networking 
 
-As you have seen above a standard installation of Docker Desktop gives us a pre-built network called `bridge` If you look back up to the `docker network list` command, you will see that the networked called bridge is associated with the `bridge` driver. Just because they have the same name doesn't they are the same thing. Connected but not the same thing. 
+As you have seen above a standard installation of Docker Desktop gives us a pre-built network called `bridge` If you look back up to the `docker network list` command, you will see that the network called bridge is associated with the `bridge` driver. Just because they have the same name doesn't they are the same thing. Connected but not the same thing. 
 
 The output above also shows that the bridge network is scoped locally. This means that the network only exists on this Docker host. This is true of all networks using the bridge driver - the bridge driver provides single-host networking.
 
@@ -43,7 +43,7 @@ All networks created with the bridge driver are based on a Linux bridge (a.k.a.
 
 By default the bridge network is assigned to new containers, meaning unless you specify a network all containers will be connected to the bridge network. 
 
-Lets create a new container with the command `docker run -dt ubuntu sleep infinity`
+Let's create a new container with the command `docker run -dt ubuntu sleep infinity`
 
 The sleep command above is just going to keep the container running in the background so we can mess around with it. 
 
@@ -59,24 +59,23 @@ From here our image doesn't have anything to ping so we need to run the followin
 
 ![](Images/Day47_Containers6.png)
 
-To clear this up we can run `docker stop 3a99af449ca2` again use `docker ps` to find your container ID but this will remove our container. 
+To clear this up we can run `docker stop 3a99af449ca2` again and use `docker ps` to find your container ID but this will remove our container. 
 
 ### Configure NAT for external connectivity 
 
-In this step we'll start a new NGINX container and map port 8080 on the Docker host to port 80 inside of the container. This means that traffic that hits the Docker host on port 8080 will be passed on to port 80 inside the container.
+In this step, we'll start a new NGINX container and map port 8080 on the Docker host to port 80 inside of the container. This means that traffic that hits the Docker host on port 8080 will be passed on to port 80 inside the container.
 
-Start a new container based off the official NGINX image by running `docker run --name web1 -d -p 8080:80 nginx`
+Start a new container based on the official NGINX image by running `docker run --name web1 -d -p 8080:80 nginx`
 
 ![](Images/Day47_Containers7.png)
 
-
 Review the container status and port mappings by running `docker ps`
 
 ![](Images/Day47_Containers8.png)
 
-The top line shows the new web1 container running NGINX. Take note of the command the container is running as well as the port mapping - `0.0.0.0:8080->80/tcp` maps port 8080 on all host interfaces to port 80 inside the web1 container. This port mapping is what effectively makes the containers web service accessible from external sources (via the Docker hosts IP address on port 8080).
+The top line shows the new web1 container running NGINX. Take note of the command the container is running as well as the port mapping - `0.0.0.0:8080->80/tcp` maps port 8080 on all host interfaces to port 80 inside the web1 container. This port mapping is what effectively makes the container's web service accessible from external sources (via the Docker hosts IP address on port 8080).
 
-Now we need our IP address for our actual host, we can do this by going into our WSL terminal and using the `ip addr` command. 
+Now we need our IP address for our actual host, we can do this by going into our WSL terminal and using the `IP addr` command. 
 
 ![](Images/Day47_Containers9.png)
 
@@ -84,19 +83,19 @@ Then we can take this IP and open a browser and head to `http://172.25.218.154:8
 
 ![](Images/Day47_Containers10.png)
 
-I have taken these instructions from this site from way back in 2017 DockerCon but they are still relevant today. However the rest of the walkthrough goes into Docker Swarm and I am not going to be looking into that here. [Docker Networking - DockerCon 2017](https://github.com/docker/labs/tree/master/dockercon-us-2017/docker-networking)
+I have taken these instructions from this site from way back in 2017 DockerCon but they are still relevant today. However, the rest of the walkthrough goes into Docker Swarm and I am not going to be looking into that here. [Docker Networking - DockerCon 2017](https://github.com/docker/labs/tree/master/dockercon-us-2017/docker-networking)
 
 ### Securing your containers 
 
-Containers provide a secure environment for your workloads vs a full server configuration. They offer the ability to break up your applications into much smaller, loosly coupled components each isolated from one another which helps resude the attack surface overall. 
+Containers provide a secure environment for your workloads vs a full server configuration. They offer the ability to break up your applications into much smaller, loosely coupled components each isolated from one another which helps reduce the attack surface overall. 
 
 But they are not immune from hackers that are looking to exploit systems. We still need to understand the security pitfalls of the technology and maintain best practices. 
 
 ### Move away from root permission 
 
-All of the containers we have deployed have been using the root permission to the process within your containers. Which means they have full administrative access to your container and host environments. Now for the purposes of walking through we knew these systems were not going to be up and running for long. But you saw how easy it was to get up and running. 
+All of the containers we have deployed have been using the root permission to the process within your containers. This means they have full administrative access to your container and host environments. Now to walk through we knew these systems were not going to be up and running for long. But you saw how easy it was to get up and running. 
 
-We can add a few steps to our process to enable non root users to be our preferred best practice. When creating our dockerfile we can create user accounts. You can find this example also in the containers folder in the repository. 
+We can add a few steps to our process to enable non-root users to be our preferred best practice. When creating our dockerfile we can create user accounts. You can find this example also in the containers folder in the repository. 
 
 ```
 # Use the official Ubuntu 18.04 as base
@@ -112,9 +111,9 @@ However, this method doesn’t address the underlying security flaw of the image
 
 ### Private Registry
 
-Another area we have used heavily is public registries in DockerHub, with a private registry of container images set up by your organisation means that you can host where you wish or there are managed services for this as well, but all in all this gives you complete control of the images available for you and your team. 
+Another area we have used heavily in public registries in DockerHub, with a private registry of container images set up by your organisation means that you can host where you wish or there are managed services for this as well, but all in all, this gives you complete control of the images available for you and your team. 
 
-DockerHub is great to give you a baseline, but its only going to be providing you with a basic service where you have to put a lot of trust into the image publisher. 
+DockerHub is great to give you a baseline, but it's only going to be providing you with a basic service where you have to put a lot of trust into the image publisher. 
 
 ### Lean & Clean 
 
@@ -132,8 +131,8 @@ Checking `docker image` is a great command to see the size of your images.
 - [Programming with Mosh - Docker Tutorial for Beginners](https://www.youtube.com/watch?v=pTFZFxd4hOI)
 - [Docker Tutorial for Beginners - What is Docker? Introduction to Containers](https://www.youtube.com/watch?v=17Bl31rlnRM&list=WL&index=128&t=61s)
 - [WSL 2 with Docker getting started](https://www.youtube.com/watch?v=5RQbdMn04Oc)
-- [Blog on gettng started building a docker image](https://stackify.com/docker-build-a-beginners-guide-to-building-docker-images/)
+- [Blog on getting started building a docker image](https://stackify.com/docker-build-a-beginners-guide-to-building-docker-images/)
 - [Docker documentation for building an image](https://docs.docker.com/develop/develop-images/dockerfile_best-practices/)
 - [YAML Tutorial: Everything You Need to Get Started in Minute](https://www.cloudbees.com/blog/yaml-tutorial-everything-you-need-get-started)
 
-See you on [Day 48](day48.md) 
+See you on [Day 48](day48.md)