Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletter Hub
Free Learning
Arrow right icon
timer SALE ENDS IN
0 Days
:
00 Hours
:
00 Minutes
:
00 Seconds
Arrow up icon
GO TO TOP
Learn Docker - Fundamentals of Docker 18.x

You're reading from   Learn Docker - Fundamentals of Docker 18.x Everything you need to know about containerizing your applications and running them in production

Arrow left icon
Product type Paperback
Published in Apr 2018
Publisher Packt
ISBN-13 9781788997027
Length 398 pages
Edition 1st Edition
Tools
Arrow right icon
Author (1):
Arrow left icon
Dr. Gabriel N. Schenker Dr. Gabriel N. Schenker
Author Profile Icon Dr. Gabriel N. Schenker
Dr. Gabriel N. Schenker
Arrow right icon
View More author details
Toc

Table of Contents (21) Chapters Close

Title Page
Packt Upsell
Contributors
Preface
1. What Are Containers and Why Should I Use Them? 2. Setting up a Working Environment FREE CHAPTER 3. Working with Containers 4. Creating and Managing Container Images 5. Data Volumes and System Management 6. Distributed Application Architecture 7. Single-Host Networking 8. Docker Compose 9. Orchestrators 10. Introduction to Docker Swarm 11. Zero Downtime Deployments and Secrets 12. Introduction to Kubernetes 13. Deploying, Updating, and Securing an Application with Kubernetes 14. Running a Containerized App in the Cloud 1. Assessment 2. Other Books You May Enjoy Index

Chapter 7


  1. The three core elements are sandbox, endpoint, and network
  2. Execute this command:
$ docker network create --driver bridge frontend
  1. Run this command:
$ docker container run -d --name n1 \
    --network frontend -p 8080:80 nginx:alpine
$ docker container run -d --name n2 \
    --network frontend -p 8081:80 nginx:alpine

Test that both Nginx instances are up and running:

$ curl -4 localhost:8080
$ curl -4 localhost:8081

You should be seeing the welcome page of Nginx in both cases.

  1. To get the IPs of all attached containers, run:
$ docker network inspect frontend | grep IPv4Address

You should see something similar to the following:

"IPv4Address": "172.18.0.2/16",
"IPv4Address": "172.18.0.3/16",

To get the subnet used by the network, use the following (for example):

$ docker network inspect frontend | grep subnet

You should receive something along the lines of the following (obtained from the previous example):

"Subnet": "172.18.0.0/16",
  1. The host network allows us to run a container in the networking namespace of the host.
  2. Only use this network for debugging purposes or when building a system-level tool. Never use the host network for an application container running production!
  3. The none network is basically saying that the container is not attached to any network. It should be used for containers that do not need to communicate with other containers and do not need to be accessed from outside.
  4. The none network could e.g. be used for a batch process running in a container that only needs access to local resources such as files which could be accessed via a host mounted volume.
lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $15.99/month. Cancel anytime
Visually different images