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
Docker and Kubernetes for Java Developers

You're reading from   Docker and Kubernetes for Java Developers Scale, deploy, and monitor multi-container applications

Arrow left icon
Product type Paperback
Published in Aug 2017
Publisher Packt
ISBN-13 9781786468390
Length 318 pages
Edition 1st Edition
Languages
Tools
Arrow right icon
Authors (2):
Arrow left icon
Jaroslaw Krochmalski Jaroslaw Krochmalski
Author Profile Icon Jaroslaw Krochmalski
Jaroslaw Krochmalski
 Krochmalski Krochmalski
Author Profile Icon Krochmalski
Krochmalski
Arrow right icon
View More author details
Toc

Table of Contents (18) Chapters Close

Title Page
Credits
About the Author
About the Reviewer
www.PacktPub.com
Customer Feedback
Preface
1. Introduction to Docker FREE CHAPTER 2. Networking and Persistent Storage 3. Working with Microservices 4. Creating Java Microservices 5. Creating Images with Java Applications 6. Running Containers with Java Applications 7. Introduction to Kubernetes 8. Using Kubernetes with Java 9. Working with the Kubernetes API 10. Deploying Java on Kubernetes in the Cloud 11. More Resources

Creating and inspecting a network


Let's create a network. We are going to call our network myNetwork. Execute the following command from the shell or command line:

$ docker network create myNetwork

This is the simplest form of the command, and yet it will probably be used the most often. It takes a default driver (we haven't used any option to specify a driver, we will just use the default one, which is bridge). As the output, Docker will print out the identifier of the newly created network:

You will later use this identifier to refer to this network when connecting containers to it or inspecting the network's properties. The last parameter of the command is the network's name, which is a lot more convenient and easier to remember than the ID. The network name in our case is myNetwork. The docker network create command takes more parameters, as shown in the following table:

Option

Description

-d, -driver="bridge"

Driver to manage the network

-aux-address=map[]

Auxiliary IPv4 or IPv6 addresses used...

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 £13.99/month. Cancel anytime
Visually different images