You will need the following things to get the most out of this book:

• An understanding of current software development, DevOps, and system admin concepts.
• A basic understanding of container—start here: https://training.play-with-docker.com/ops-stage1/.
• Docker (CE) Desktop for Mac or Windows is helpful.
• Access to four Linux hosts (bare-metal or VMs) and an optional Windows Server 2016 host (bare-metal or VM) is ideal to try your own PoC. Cloud VMs can also be used, but we don't cover cloud-specific installs in the examples.

You can download the example code files for this book from your account at www.packt.com. If you purchased this book elsewhere, you can visit www.packt.com/support and register to have the files emailed directly to you.

You can download the code files by following these steps:

1. Log in or register at www.packt.com.
2. Select the SUPPORT tab.
3. Click on Code Downloads & Errata.
4. Enter the name of the book in the Search box and follow the onscreen instructions.

Once the file is downloaded, please make sure that you unzip or extract the folder using the latest version of:

• WinRAR/7-Zip for Windows
• Zipeg/iZip/UnRarX for Mac
• 7-Zip/PeaZip for Linux

The code bundle for the book is also hosted on GitHub at https://github.com/PacktPublishing/Mastering-Docker-Enterprise. In case there's an update to the code, it will be updated on the existing GitHub repository.

We also have other code bundles from our rich catalog of books and videos available at https://github.com/PacktPublishing/. Check them out!

We also provide a PDF file that has color images of the screenshots/diagrams used in this book. You can download it here: https://www.packtpub.com/sites/default/files/downloads/9781789612073_ColorImages.pdf.

There are a number of text conventions used throughout this book.

CodeInText: Indicates code words in text, database table names, folder names, filenames, file extensions, pathnames, dummy URLs, user input, and Twitter handles. Here is an example: "Generally speaking, sudo service docker restart should do the trick."

A block of code is set as follows:

{
"log-driver": "json-file",
"log-opts": {
    "max-size": "10m",
    "max-file": "3"
    },
"live-restore": true
}

When we wish to draw your attention to a particular part of a code block, the relevant lines or items are set in bold:

mta-netfx-dev
    ├── docker
    │   ├── web
    │   │   └── Dockerfile
    │   └── web-builder
    │       └── 3.5
    │           └── Dockerfile

Any command-line input or output is written as follows:

$ docker container run -d -p 5432:5432 db-image:v1
1fe040d1acf242d4cfdb47761db2a59f1bb44b5eedf17376b9455120d86281a5

Bold: Indicates a new term, an important word, or words that you see onscreen. For example, words in menus or dialog boxes appear in the text like this. Here is an example: "Expand the admin menu and click My Profile."