This commit is contained in:
Chris Chinchilla 2023-03-01 12:51:40 +01:00
parent c8b630087e
commit 5f613c757a
6 changed files with 15 additions and 12 deletions

View File

@ -64,3 +64,5 @@ XWiki
Zsh Zsh
macOS macOS
minikube minikube
sandbox
sandboxed

View File

@ -6,7 +6,7 @@ redirect_from:
description: Containerize and run a simple application to learn Docker description: Containerize and run a simple application to learn Docker
--- ---
For the rest of this guide, you will be working with a simple todo For the rest of this guide, you'll be working with a simple todo
list manager that's running in Node.js. If you're not familiar with Node.js, list manager that's running in Node.js. If you're not familiar with Node.js,
don't worry. This guide doesn't require JavaScript experience. don't worry. This guide doesn't require JavaScript experience.

View File

@ -83,7 +83,7 @@ To remove a container, you first need to stop it. Once it has stopped, you can r
### Remove a container using Docker Desktop ### Remove a container using Docker Desktop
1. Open Docker Desktop to the **Containers** view. 1. Open Docker Desktop to the **Containers** view.
2. Select the trash can icon under the **Actions** column for the old container that you want to delete. 2. Select the trash can icon under the **Actions** column for the old, currently running container that you want to delete.
3. In the confirmation dialog, select **Delete forever**. 3. In the confirmation dialog, select **Delete forever**.
<hr> <hr>

View File

@ -53,7 +53,8 @@ What you'll see is that the files created in one container aren't available in a
$ docker run -it ubuntu ls / $ docker run -it ubuntu ls /
``` ```
And look! There's no `data.txt` file there! That's because it was written to the scratch space for In this case the command lists the files in the root directory of the container.
Look, there's no `data.txt` file there! That's because it was written to the scratch space for
only the first container. only the first container.
4. Go ahead and remove the first container using the `docker rm -f <container-id>` command. 4. Go ahead and remove the first container using the `docker rm -f <container-id>` command.

View File

@ -6,7 +6,7 @@ keywords: >
description: Using bind mounts in our application description: Using bind mounts in our application
--- ---
In the previous chapter, we talked about and used a volume mount to persist the In [part 5](./05_persisting_data.md), we talked about and used a volume mount to persist the
data in our database. A volume mount is a great choice when you need somewhere data in our database. A volume mount is a great choice when you need somewhere
persistent to store your application data. persistent to store your application data.

View File

@ -61,10 +61,10 @@ Welcome! We're excited that you want to learn Docker.
This guide contains step-by-step instructions on how to get started with Docker. Some of the things you'll learn and do in this guide are: This guide contains step-by-step instructions on how to get started with Docker. Some of the things you'll learn and do in this guide are:
- Build and run an image as a container - Build and run an image as a container.
- Share images using Docker Hub - Share images using Docker Hub.
- Deploy Docker applications using multiple containers with a database - Deploy Docker applications using multiple containers with a database.
- Run applications using Docker Compose - Run applications using Docker Compose.
Before you get to the hands on part of the guide, you should learn about containers and images. Before you get to the hands on part of the guide, you should learn about containers and images.
@ -73,10 +73,10 @@ Before you get to the hands on part of the guide, you should learn about contain
Simply put, a container is a sandboxed process on your machine that is isolated from all other processes on the host machine. That isolation leverages [kernel namespaces and cgroups](https://medium.com/@saschagrunert/demystifying-containers-part-i-kernel-space-2c53d6979504), Simply put, a container is a sandboxed process on your machine that is isolated from all other processes on the host machine. That isolation leverages [kernel namespaces and cgroups](https://medium.com/@saschagrunert/demystifying-containers-part-i-kernel-space-2c53d6979504),
features that have been in Linux for a long time. Docker has worked to make these capabilities approachable and easy to use. To summarize, a container: features that have been in Linux for a long time. Docker has worked to make these capabilities approachable and easy to use. To summarize, a container:
- is a runnable instance of an image. You can create, start, stop, move, or delete a container using the DockerAPI or CLI. - Is a runnable instance of an image. You can create, start, stop, move, or delete a container using the DockerAPI or CLI.
- can be run on local machines, virtual machines or deployed to the cloud. - Can be run on local machines, virtual machines or deployed to the cloud.
- is portable (can be run on any OS). - Is portable (can be run on any OS).
- is isolated from other containers and runs its own software, binaries, and configurations. - Is isolated from other containers and runs its own software, binaries, and configurations.
## What is a container image? ## What is a container image?