docker
/
docs
mirror of https://github.com/docker/docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Draft

This commit is contained in:
Chris Chinchilla 2023-03-01 16:13:24 +01:00
parent ffd2a8d680
commit 5f610a9961
3 changed files with 6 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
get-started/06_bind_mounts.md
View File

@ -157,7 +157,7 @@ So, let's do it!
server. If we look in the `package.json`, we'll see that the `dev` script
starts `nodemon`.
3. You can watch the logs using `docker logs`. You'll know you're ready to go
3. You can watch the logs using `docker logs <container-id>`. You'll know you're ready to go
when you see this:
```console

5
get-started/08_using_compose.md
View File

@ -29,7 +29,7 @@ $ docker compose version
## Create the Compose file
1. At the root of the app project, create a file named `docker-compose.yml`.
1. At the root of the `/getting-started/app` folder, create a file named `docker-compose.yml`.
2. In the compose file, we'll start off by defining the list of services (or containers) we want to run as part of our application.
@ -190,7 +190,6 @@ At this point, our complete `docker-compose.yml` should look like this:
```yaml
services:
app:
image: node:18-alpine
@ -278,7 +277,7 @@ Compose and used to group the containers together. By default, the project name
![Docker Dashboard with app project](images/dashboard-app-project-collapsed.png)
If you twirl down the app, you will see the two containers we defined in the compose file. The names are also a little
If you click the disclose arrow next to **app**, you will see the two containers we defined in the compose file. The names are also a little
more descriptive, as they follow the pattern of `<service-name>-<replica-number>`. So, it's very easy to
quickly see what container is our app and which container is the mysql database.

6
get-started/11_what_next.md
View File

@ -4,7 +4,7 @@ keywords: get started, setup, orientation, quickstart, intro, concepts, containe
description: Making sure you have more ideas of what you could do next with your application
---
Although we're done with our workshop, there's still a LOT more to learn about containers!
Although we're done with our get started guide, there's still a LOT more to learn about containers!
We're not going to go deep-dive here, but here are a few other areas to look at next!
## Container orchestration
@ -44,9 +44,9 @@ We recommend the video workshop from DockerCon 2022. Watch the video below or us
## Creating a container from scratch
If you'd like to see how containers are built from scratch, Liz Rice from Aqua Security has a fantastic talk in which she creates a container from scratch in Go. While the talk does not go into networking, using images for the filesystem, and other advanced topics, it gives a deep dive into how things are working.
If you'd like to see how containers are built from scratch, Liz Rice from Aqua Security has a fantastic talk in which she creates a container from scratch in Go. While the talk does not go into networking, using images for the filesystem, and other advanced topics, it gives a deep dive into how things are working.
<iframe src="https://www.youtube-nocookie.com/embed/8fi7uSYlOdc" style="max-width: 100%; aspect-ratio: 16 / 9;" width="560" height="auto" frameborder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
<iframe src="https://www.youtube-nocookie.com/embed/8fi7uSYlOdc" style="max-width: 100%; aspect-ratio: 16 / 9;" width="560" height="auto" frameborder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
## Language-specific guides