Skip to content

Commit 7ab3ae0

Browse files
committed
freshness and content edits
1 parent 1c0215e commit 7ab3ae0

14 files changed

Lines changed: 94 additions & 107 deletions

learn-pr/azure/intro-to-docker-containers/1-introduction.yml

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,12 +5,11 @@ title: Introduction
55
metadata:
66
title: Introduction
77
description: Introduction
8-
ms.date: 10/09/2024
8+
ms.date: 03/20/2026
99
author: davidsmatlak
1010
ms.author: davidsmatlak
1111
ms.topic: unit
1212

1313
durationInMinutes: 1
1414
content: |
1515
[!include[](includes/1-introduction.md)]
16-

learn-pr/azure/intro-to-docker-containers/2-what-is-docker.yml

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,12 +5,11 @@ title: What is Docker?
55
metadata:
66
title: What is Docker?
77
description: In this unit, we discuss what Docker is and its architecture.
8-
ms.date: 10/09/2024
8+
ms.date: 03/20/2026
99
author: davidsmatlak
1010
ms.author: davidsmatlak
1111
ms.topic: unit
1212

1313
durationInMinutes: 5
1414
content: |
1515
[!include[](includes/2-what-is-docker.md)]
16-

learn-pr/azure/intro-to-docker-containers/3-how-docker-images-work.yml

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ title: How Docker images work
55
metadata:
66
title: How Docker images work
77
description: In this unit, we discuss how we build Docker images and explore basic image management.
8-
ms.date: 10/09/2024
8+
ms.date: 03/20/2026
99
author: davidsmatlak
1010
ms.author: davidsmatlak
1111
ms.topic: unit
@@ -52,4 +52,3 @@ quiz:
5252
- content: "A container image is a read-only portable package that contains software."
5353
isCorrect: false
5454
explanation: "A container image is an immutable package that contains all the application code, system packages, binaries, libraries, configuration files, and the operating system running in the container."
55-

learn-pr/azure/intro-to-docker-containers/4-how-docker-containers-work.yml

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ title: How Docker containers work
55
metadata:
66
title: How Docker containers work
77
description: In this unit, we explore how Docker containers work and how to run containers. We also discuss the life cycle of a Docker container.
8-
ms.date: 10/09/2024
8+
ms.date: 03/20/2026
99
author: davidsmatlak
1010
ms.author: davidsmatlak
1111
ms.topic: unit
@@ -28,7 +28,7 @@ quiz:
2828
- content: "host"
2929
isCorrect: false
3030
explanation: "The Host network configuration allows the container to use the host's IP address and ports. The publish flag isn't used with this network."
31-
31+
3232
- content: "Which storage option is the best choice that allows the host and container to share a file to manage name server resolution; for example, the resolve.conf file on Linux?"
3333
choices:
3434
- content: "A volume"
@@ -37,4 +37,3 @@ quiz:
3737
- content: "Bind mount"
3838
isCorrect: true
3939
explanation: "A bind mount, like a volume, is stored on the host filesystem at a specific folder location. However, the host is expected to update bind mount data. The resolve.conf contents is expected to change by the host and used by both the container and host."
40-

learn-pr/azure/intro-to-docker-containers/5-when-use-docker-containers.yml

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,12 +5,11 @@ title: When to use Docker containers
55
metadata:
66
title: When to use Docker containers
77
description: In this unit, you'll see the benefits of using Docker as well as some considerations to help you decide when to use Docker.
8-
ms.date: 10/09/2024
8+
ms.date: 03/20/2026
99
author: davidsmatlak
1010
ms.author: davidsmatlak
1111
ms.topic: unit
1212

1313
durationInMinutes: 5
1414
content: |
1515
[!include[](includes/5-when-use-docker-containers.md)]
16-

learn-pr/azure/intro-to-docker-containers/6-summary.yml

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,11 +5,10 @@ title: Summary
55
metadata:
66
title: Summary
77
description: Summary
8-
ms.date: 10/09/2024
8+
ms.date: 03/20/2026
99
author: davidsmatlak
1010
ms.author: davidsmatlak
1111
ms.topic: unit
1212
durationInMinutes: 1
1313
content: |
1414
[!include[](includes/6-summary.md)]
15-

learn-pr/azure/intro-to-docker-containers/includes/1-introduction.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,9 +2,9 @@ Teams today must release apps quickly to attract and keep business. This require
22

33
The idea of using software containerization technology as a time-saving and cost-reduction solution is popular. One of containerization's strengths is that you don't have to configure hardware and spend time installing operating systems and software to host a deployment. Containers are isolated from each other, and multiple containers can run on the same hardware. This configuration helps us use hardware more efficiently and can help improve our application's security.
44

5-
Suppose you work for an online clothing retailer that's planning to develop several internal apps. Your team develops and tests all applications on-premises, then deploys them to Azure for pre-production testing and final production hosting. You're looking for maximum compatibility in each environment with little or no configuration changes. Using Docker as a containerization solution seems an ideal choice.
5+
Suppose you work for an online clothing retailer that's planning to develop several internal apps. Your team develops and tests all applications on-premises, then deploys them to Azure for preproduction testing and final production hosting. You're looking for maximum compatibility in each environment with little or no configuration changes. Using Docker as a containerization solution seems an ideal choice.
66

7-
Here, you'll learn how you can use Docker to create your own containers. You'll also learn a bit about how Docker infrastructure works behind the scenes. The goal is to help you decide if Docker containers are the right choice for your business.
7+
In this module, you learn how you can use Docker to create your own containers. You also learn a bit about how Docker infrastructure works behind the scenes. The goal is to help you decide if Docker containers are the right choice for your business.
88

99
## Learning objectives
1010

learn-pr/azure/intro-to-docker-containers/includes/2-what-is-docker.md

Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -1,32 +1,32 @@
1-
Before we start our quick tour of Docker containers, let's have a look at how our team develops and deploys applications. We'll also briefly describe some of the challenges our teams face.
1+
Before we start our quick tour of Docker containers, let's have a look at how our team develops and deploys applications. We also describe some of the challenges our teams face.
22

33
The process of developing and managing applications in your company typically includes one or more teams. There's a development team that creates the software and an operations team responsible for deploying these applications. The operations team is also responsible for managing the application-hosting infrastructure.
44

5-
For example, assume we're developing an order-tracking portal for our company's various outlets to use. Several environments host our applications during the app's development and publishing process. First, the development team develops and tests the software in a development environment. From here, the software is then deployed to a quality assurance (QA) environment, followed by pre-production, and a final production environment.
5+
For example, assume we're developing an order-tracking portal for our company's various outlets to use. Several environments host our applications during the app's development and publishing process. To begin, the development team develops and tests the software in a development environment. Next, the software is deployed to a quality assurance (QA) environment, followed by preproduction, and then a final production environment.
66

7-
There are several challenges that we'll need to consider in the preceding scenario:
7+
The software development process has several challenges that we need to consider:
88

99
- **Managing hosting environments**
1010

11-
The different environments all require both software and hardware management. We have to ensure that both the installed software and configured hardware in each is the same. We also need to configure aspects such as network access, data storage, and security per environment in a consistent and easily reproducible manner.
11+
The different environments all require both software and hardware management. We must ensure that both the installed software and configured hardware in each is the same. We also need to configure aspects like network access, data storage, and security per environment in a consistent and easily reproducible manner.
1212

1313
- **Continuity in software delivery**
1414

15-
Deploying applications to our environments must happen consistently. Each deployment package must include all system packages, binaries, libraries, configuration files, and other items that ensure a fully functional application. We also need to make sure that all of these dependencies match software versions and architecture.
15+
Deploying applications to our environments must be consistent. Each deployment package must include all system packages, binaries, libraries, configuration files, and other items that ensure a fully functional application. We also need to make sure that all of these dependencies match software versions and architecture.
1616

1717
- **Efficient hardware use**
1818

19-
Each deployed application must execute in such a way that it's isolated from other applications running on the same hardware. We aim to run more than one application per server to make the best use of resources without compromising each other.
19+
Each deployed application must be isolated from other applications that run on the same hardware. We want to run more than one application per server to make the best use of resources without compromising each other.
2020

2121
- **Application portability**
2222

2323
There are several reasons why application portability is essential. A hosting environment might fail, or we might need to scale out our application. In both instances, the potential result is redeploying our software to a new environment. We want to move software from one host to another, even if the underlying infrastructure is different. Such a move needs to happen as fast as possible to reduce downtime for our customers.
2424

25-
Before we look at the Docker features that help solve these challenges, we'll discuss a few concepts and look at a brief overview of the Docker architecture.
25+
Before we look at the Docker features that help solve these challenges, we discuss a few concepts and look at a brief overview of the Docker architecture.
2626

2727
## What is a container?
2828

29-
A container is a loosely isolated environment that allows us to build and run software packages. These software packages include the code and all dependencies to run applications quickly and reliably on any computing environment. We call these packages _container images_.
29+
A container is an isolated environment that allows us to build and run software packages. These software packages include the code and all dependencies to run applications on any computing environment. We call these packages _container images_.
3030

3131
The container image becomes the unit we use to distribute our applications.
3232

@@ -49,7 +49,7 @@ The Docker Engine consists of several components configured as a client-server i
4949
:::image type="complex" source="../media/2-docker-architecture.svg" alt-text="Diagram showing a high-level overview of the Docker architecture.":::
5050
The diagram shows a square that represents Docker Hub with container images and a separate square that represents a Docker Host. An arrow shows communication between the Docker Hub and Docker Host.
5151

52-
The Docker Host contains two objects. One represents the Docker Engine, and the second the running docker containers. The Docker Host object contains four objects. These are the Docker Server, the Docker REST API, the Docker Client, and stored container images.
52+
The Docker Host contains two objects. One represents the Docker Engine, and the second is the Docker containers. The Docker Host object contains four objects. The objects are the Docker Server, the Docker REST API, the Docker Client, and stored container images.
5353

5454
Some arrows show communication between the Docker Server, the REST API, and the Docker Client. These arrows indicate how the user communicates with the Docker Server via the REST API.
5555

@@ -66,7 +66,7 @@ The Docker server is a daemon named `dockerd`. The `dockerd` daemon responds to
6666

6767
#### Docker objects
6868

69-
There are several objects that you'll create and configure to support your container deployments. These include networks, storage volumes, plugins, and other service objects. We won't cover all of these objects here, but it's good to keep in mind that these objects are items that we can create and deploy as needed.
69+
There are several objects that you create and configure to support your container deployments. These objects include networks, storage volumes, plugins, and other service objects. This module doesn't mention all of these objects, but it's good to keep in mind that these objects are items that we can create and deploy as needed.
7070

7171
### Docker Hub
7272

0 commit comments

Comments
 (0)