Skip to content

Commit 658092c

Browse files
committed
update ordered lists to fix yaml formatting issues
1 parent 8a93a1c commit 658092c

4 files changed

Lines changed: 36 additions & 37 deletions

File tree

get-started/index.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -59,11 +59,11 @@ redirect_from:
5959

6060
Welcome! We are excited that you want to learn Docker. The Docker Quickstart training module teaches you how to:
6161

62-
1. Set up your Docker environment (on this page)
62+
1. Set up your Docker environment (on this page)
6363

64-
2. [Build and run your image](part2.md)
64+
2. [Build and run your image](part2.md)
6565

66-
3. [Share images on Docker Hub](part3.md)
66+
3. [Share images on Docker Hub](part3.md)
6767

6868
## Docker concepts
6969

@@ -125,7 +125,7 @@ Docker version 19.03.5, build 633a0ea
125125

126126
### Test Docker installation
127127

128-
1. Test that your installation works by running the [hello-world](https://hub.docker.com/_/hello-world/){: target="_blank" class="_"} Docker image:
128+
1. Test that your installation works by running the [hello-world](https://hub.docker.com/_/hello-world/){: target="_blank" class="_"} Docker image:
129129

130130
```shell
131131
$ docker run hello-world
@@ -141,9 +141,9 @@ Docker version 19.03.5, build 633a0ea
141141
...
142142
```
143143

144-
2. Run `docker image ls` to list the `hello-world` image that you downloaded to your machine.
144+
2. Run `docker image ls` to list the `hello-world` image that you downloaded to your machine.
145145

146-
3. List the `hello-world` container (spawned by the image) which exits after displaying its message. If it is still running, you do not need the `--all` option:
146+
3. List the `hello-world` container (spawned by the image) which exits after displaying its message. If it is still running, you do not need the `--all` option:
147147

148148
```shell
149149
$ docker container ls --all

get-started/orchestration.md

Lines changed: 21 additions & 21 deletions
Original file line numberDiff line numberDiff line change
@@ -49,13 +49,13 @@ Docker Desktop will set up Kubernetes for you quickly and easily. Follow the set
4949
5050
This describes a pod with a single container, isolating a simple ping to 8.8.8.8.
5151
52-
4. In a terminal, navigate to where you created `pod.yaml` and create your pod:
52+
4. In a terminal, navigate to where you created `pod.yaml` and create your pod:
5353

5454
```shell
5555
kubectl apply -f pod.yaml
5656
```
5757

58-
5. Check that your pod is up and running:
58+
5. Check that your pod is up and running:
5959

6060
```shell
6161
kubectl get pods
@@ -68,7 +68,7 @@ Docker Desktop will set up Kubernetes for you quickly and easily. Follow the set
6868
demo 1/1 Running 0 4s
6969
```
7070

71-
6. Check that you get the logs you'd expect for a ping process:
71+
6. Check that you get the logs you'd expect for a ping process:
7272

7373
```shell
7474
kubectl logs demo
@@ -84,7 +84,7 @@ Docker Desktop will set up Kubernetes for you quickly and easily. Follow the set
8484
...
8585
```
8686

87-
7. Finally, tear down your test pod:
87+
7. Finally, tear down your test pod:
8888

8989
```shell
9090
kubectl delete -f pod.yaml
@@ -99,11 +99,11 @@ Docker Desktop will set up Kubernetes for you quickly and easily. Follow the set
9999

100100
### Windows
101101

102-
1. After installing Docker Desktop, you should see a Docker icon in your system tray. Right-click on it, and navigate **Settings** > **Kubernetes**.
102+
1. After installing Docker Desktop, you should see a Docker icon in your system tray. Right-click on it, and navigate **Settings** > **Kubernetes**.
103103

104-
2. Check the checkbox labeled **Enable Kubernetes**, and click **Apply & Restart**. Docker Desktop will automatically set up Kubernetes for you. You'll know that Kubernetes has been successfully enabled when you see a green light beside 'Kubernetes _running_' in the **Settings** menu.
104+
2. Check the checkbox labeled **Enable Kubernetes**, and click **Apply & Restart**. Docker Desktop will automatically set up Kubernetes for you. You'll know that Kubernetes has been successfully enabled when you see a green light beside 'Kubernetes _running_' in the **Settings** menu.
105105

106-
3. In order to confirm that Kubernetes is up and running, create a text file called `pod.yaml` with the following content:
106+
3. In order to confirm that Kubernetes is up and running, create a text file called `pod.yaml` with the following content:
107107

108108
```yaml
109109
apiVersion: v1
@@ -119,13 +119,13 @@ Docker Desktop will set up Kubernetes for you quickly and easily. Follow the set
119119

120120
This describes a pod with a single container, isolating a simple ping to 8.8.8.8.
121121

122-
4. In PowerShell, navigate to where you created `pod.yaml` and create your pod:
122+
4. In PowerShell, navigate to where you created `pod.yaml` and create your pod:
123123

124124
```shell
125125
kubectl apply -f pod.yaml
126126
```
127127

128-
5. Check that your pod is up and running:
128+
5. Check that your pod is up and running:
129129

130130
```shell
131131
kubectl get pods
@@ -138,7 +138,7 @@ Docker Desktop will set up Kubernetes for you quickly and easily. Follow the set
138138
demo 1/1 Running 0 4s
139139
```
140140

141-
6. Check that you get the logs you'd expect for a ping process:
141+
6. Check that you get the logs you'd expect for a ping process:
142142

143143
```shell
144144
kubectl logs demo
@@ -154,7 +154,7 @@ Docker Desktop will set up Kubernetes for you quickly and easily. Follow the set
154154
...
155155
```
156156

157-
7. Finally, tear down your test pod:
157+
7. Finally, tear down your test pod:
158158

159159
```shell
160160
kubectl delete -f pod.yaml
@@ -180,7 +180,7 @@ Docker Desktop runs primarily on Docker Engine, which has everything you need to
180180

181181
### Mac
182182

183-
1. Open a terminal, and initialize Docker Swarm mode:
183+
1. Open a terminal, and initialize Docker Swarm mode:
184184

185185
```shell
186186
docker swarm init
@@ -198,13 +198,13 @@ Docker Desktop runs primarily on Docker Engine, which has everything you need to
198198
To add a manager to this swarm, run 'docker swarm join-token manager' and follow the instructions.
199199
```
200200

201-
2. Run a simple Docker service that uses an alpine-based filesystem, and isolates a ping to 8.8.8.8:
201+
2. Run a simple Docker service that uses an alpine-based filesystem, and isolates a ping to 8.8.8.8:
202202

203203
```shell
204204
docker service create --name demo alpine:3.5 ping 8.8.8.8
205205
```
206206

207-
3. Check that your service created one running container:
207+
3. Check that your service created one running container:
208208

209209
```shell
210210
docker service ps demo
@@ -217,7 +217,7 @@ Docker Desktop runs primarily on Docker Engine, which has everything you need to
217217
463j2s3y4b5o demo.1 alpine:3.5 docker-desktop Running Running 8 seconds ago
218218
```
219219

220-
4. Check that you get the logs you'd expect for a ping process:
220+
4. Check that you get the logs you'd expect for a ping process:
221221

222222
```shell
223223
docker service logs demo
@@ -233,7 +233,7 @@ Docker Desktop runs primarily on Docker Engine, which has everything you need to
233233
...
234234
```
235235

236-
5. Finally, tear down your test service:
236+
5. Finally, tear down your test service:
237237

238238
```shell
239239
docker service rm demo
@@ -248,7 +248,7 @@ Docker Desktop runs primarily on Docker Engine, which has everything you need to
248248

249249
### Windows
250250

251-
1. Open a powershell, and initialize Docker Swarm mode:
251+
1. Open a powershell, and initialize Docker Swarm mode:
252252

253253
```shell
254254
docker swarm init
@@ -266,13 +266,13 @@ Docker Desktop runs primarily on Docker Engine, which has everything you need to
266266
To add a manager to this swarm, run 'docker swarm join-token manager' and follow the instructions.
267267
```
268268

269-
2. Run a simple Docker service that uses an alpine-based filesystem, and isolates a ping to 8.8.8.8:
269+
2. Run a simple Docker service that uses an alpine-based filesystem, and isolates a ping to 8.8.8.8:
270270

271271
```shell
272272
docker service create --name demo alpine:3.5 ping 8.8.8.8
273273
```
274274

275-
3. Check that your service created one running container:
275+
3. Check that your service created one running container:
276276

277277
```shell
278278
docker service ps demo
@@ -285,7 +285,7 @@ Docker Desktop runs primarily on Docker Engine, which has everything you need to
285285
463j2s3y4b5o demo.1 alpine:3.5 docker-desktop Running Running 8 seconds ago
286286
```
287287

288-
4. Check that you get the logs you'd expect for a ping process:
288+
4. Check that you get the logs you'd expect for a ping process:
289289

290290
```shell
291291
docker service logs demo
@@ -301,7 +301,7 @@ Docker Desktop runs primarily on Docker Engine, which has everything you need to
301301
...
302302
```
303303

304-
5. Finally, tear down your test service:
304+
5. Finally, tear down your test service:
305305

306306
```shell
307307
docker service rm demo

get-started/part3.md

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -20,35 +20,35 @@ At this point, you've built a containerized application in [Part 2](part2.md) on
2020

2121
If you don't yet have a Docker ID, follow these steps to set one up; this will allow you to share images on Docker Hub.
2222

23-
1. Visit the Docker Hub sign up page, [https://hub.docker.com/signup](https://hub.docker.com/signup).
23+
1. Visit the Docker Hub sign up page, [https://hub.docker.com/signup](https://hub.docker.com/signup).
2424

25-
2. Fill out the form and submit to create your Docker ID.
25+
2. Fill out the form and submit to create your Docker ID.
2626

27-
3. Verify your email address to complete the registration process.
27+
3. Verify your email address to complete the registration process.
2828

29-
4. Click on the Docker icon in your toolbar or system tray, and click **Sign in / Create Docker ID**.
29+
4. Click on the Docker icon in your toolbar or system tray, and click **Sign in / Create Docker ID**.
3030

31-
5. Fill in your new Docker ID and password. After you have successfully authenticated, your Docker ID appears in the Docker Desktop menu in place of the 'Sign in' option you just used.
31+
5. Fill in your new Docker ID and password. After you have successfully authenticated, your Docker ID appears in the Docker Desktop menu in place of the 'Sign in' option you just used.
3232

3333
> You can do the same thing from the command line by typing `docker login`.
3434
3535
## Create a Docker Hub repository and push your image
3636

3737
At this point, you've set up your Docker Hub account and have connected it to your Docker Desktop. Now let's make our first repo, and share our bulletin board app there.
3838

39-
1. Click on the Docker icon in your menu bar, and navigate to **Repositories > Create**. You'll be taken to a Docker Hub page to create a new repository.
39+
1. Click on the Docker icon in your menu bar, and navigate to **Repositories > Create**. You'll be taken to a Docker Hub page to create a new repository.
4040

41-
2. Fill out the repository name as `bulletinboard`. Leave all the other options alone for now, and click **Create** at the bottom.
41+
2. Fill out the repository name as `bulletinboard`. Leave all the other options alone for now, and click **Create** at the bottom.
4242

4343
![make a repo](images/newrepo.png){:width="100%"}
4444

45-
3. Now we're ready to share our image on Docker Hub, but there's one thing we must do first: images must be *namespaced correctly* to share on Docker Hub. Specifically, images must be named like `<Docker ID>/<Repository Name>:<tag>`. We can relabel our `bulletinboard:1.0` image like this (of course, please replace `gordon` with your Docker ID):
45+
3. Now we're ready to share our image on Docker Hub, but there's one thing we must do first: images must be *namespaced correctly* to share on Docker Hub. Specifically, images must be named like `<Docker ID>/<Repository Name>:<tag>`. We can relabel our `bulletinboard:1.0` image like this (of course, please replace `gordon` with your Docker ID):
4646

4747
```shell
4848
docker image tag bulletinboard:1.0 gordon/bulletinboard:1.0
4949
```
5050

51-
4. Finally, push your image to Docker Hub:
51+
4. Finally, push your image to Docker Hub:
5252

5353
```shell
5454
docker image push gordon/bulletinboard:1.0

get-started/swarm-deploy.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,6 @@ Swarm never creates individual containers like we did in the previous step of th
2626

2727
Let's write a simple stack file to run and manage our bulletin board. Place the following in a file called `bb-stack.yaml`:
2828

29-
3029
```yaml
3130
version: '3.7'
3231

0 commit comments

Comments
 (0)