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

update ordered lists to fix yaml formatting issues

This commit is contained in:
Usha Mandya 2020-02-17 15:49:52 +00:00
parent 8a93a1ccff
commit 658092ce1f
4 changed files with 36 additions and 37 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
get-started/index.md
View File

@ -59,11 +59,11 @@ redirect_from:
Welcome! We are excited that you want to learn Docker. The Docker Quickstart training module teaches you how to:
1. Set up your Docker environment (on this page)
1. Set up your Docker environment (on this page)
2. [Build and run your image](part2.md)
2. [Build and run your image](part2.md)
3. [Share images on Docker Hub](part3.md)
3. [Share images on Docker Hub](part3.md)
## Docker concepts
@ -125,7 +125,7 @@ Docker version 19.03.5, build 633a0ea
### Test Docker installation
1. Test that your installation works by running the [hello-world](https://hub.docker.com/_/hello-world/){: target="_blank" class="_"} Docker image:
1. Test that your installation works by running the [hello-world](https://hub.docker.com/_/hello-world/){: target="_blank" class="_"} Docker image:
```shell
$ docker run hello-world
@ -141,9 +141,9 @@ Docker version 19.03.5, build 633a0ea
...
```
2. Run `docker image ls` to list the `hello-world` image that you downloaded to your machine.
2. Run `docker image ls` to list the `hello-world` image that you downloaded to your machine.
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:
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:
```shell
$ docker container ls --all

42
get-started/orchestration.md
View File

@ -49,13 +49,13 @@ Docker Desktop will set up Kubernetes for you quickly and easily. Follow the set
This describes a pod with a single container, isolating a simple ping to 8.8.8.8.
4. In a terminal, navigate to where you created `pod.yaml` and create your pod:
4. In a terminal, navigate to where you created `pod.yaml` and create your pod:
```shell
kubectl apply -f pod.yaml
```
5. Check that your pod is up and running:
5. Check that your pod is up and running:
```shell
kubectl get pods
@ -68,7 +68,7 @@ Docker Desktop will set up Kubernetes for you quickly and easily. Follow the set
demo 1/1 Running 0 4s
```
6. Check that you get the logs you'd expect for a ping process:
6. Check that you get the logs you'd expect for a ping process:
```shell
kubectl logs demo
@ -84,7 +84,7 @@ Docker Desktop will set up Kubernetes for you quickly and easily. Follow the set
...
```
7. Finally, tear down your test pod:
7. Finally, tear down your test pod:
```shell
kubectl delete -f pod.yaml
@ -99,11 +99,11 @@ Docker Desktop will set up Kubernetes for you quickly and easily. Follow the set
### Windows
1. After installing Docker Desktop, you should see a Docker icon in your system tray. Right-click on it, and navigate **Settings** > **Kubernetes**.
1. After installing Docker Desktop, you should see a Docker icon in your system tray. Right-click on it, and navigate **Settings** > **Kubernetes**.
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.
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.
3. In order to confirm that Kubernetes is up and running, create a text file called `pod.yaml` with the following content:
3. In order to confirm that Kubernetes is up and running, create a text file called `pod.yaml` with the following content:
```yaml
apiVersion: v1
@ -119,13 +119,13 @@ Docker Desktop will set up Kubernetes for you quickly and easily. Follow the set
This describes a pod with a single container, isolating a simple ping to 8.8.8.8.
4. In PowerShell, navigate to where you created `pod.yaml` and create your pod:
4. In PowerShell, navigate to where you created `pod.yaml` and create your pod:
```shell
kubectl apply -f pod.yaml
```
5. Check that your pod is up and running:
5. Check that your pod is up and running:
```shell
kubectl get pods
@ -138,7 +138,7 @@ Docker Desktop will set up Kubernetes for you quickly and easily. Follow the set
demo 1/1 Running 0 4s
```
6. Check that you get the logs you'd expect for a ping process:
6. Check that you get the logs you'd expect for a ping process:
```shell
kubectl logs demo
@ -154,7 +154,7 @@ Docker Desktop will set up Kubernetes for you quickly and easily. Follow the set
...
```
7. Finally, tear down your test pod:
7. Finally, tear down your test pod:
```shell
kubectl delete -f pod.yaml
@ -180,7 +180,7 @@ Docker Desktop runs primarily on Docker Engine, which has everything you need to
### Mac
1. Open a terminal, and initialize Docker Swarm mode:
1. Open a terminal, and initialize Docker Swarm mode:
```shell
docker swarm init
@ -198,13 +198,13 @@ Docker Desktop runs primarily on Docker Engine, which has everything you need to
To add a manager to this swarm, run 'docker swarm join-token manager' and follow the instructions.
```
2. Run a simple Docker service that uses an alpine-based filesystem, and isolates a ping to 8.8.8.8:
2. Run a simple Docker service that uses an alpine-based filesystem, and isolates a ping to 8.8.8.8:
```shell
docker service create --name demo alpine:3.5 ping 8.8.8.8
```
3. Check that your service created one running container:
3. Check that your service created one running container:
```shell
docker service ps demo
@ -217,7 +217,7 @@ Docker Desktop runs primarily on Docker Engine, which has everything you need to
463j2s3y4b5o demo.1 alpine:3.5 docker-desktop Running Running 8 seconds ago
```
4. Check that you get the logs you'd expect for a ping process:
4. Check that you get the logs you'd expect for a ping process:
```shell
docker service logs demo
@ -233,7 +233,7 @@ Docker Desktop runs primarily on Docker Engine, which has everything you need to
...
```
5. Finally, tear down your test service:
5. Finally, tear down your test service:
```shell
docker service rm demo
@ -248,7 +248,7 @@ Docker Desktop runs primarily on Docker Engine, which has everything you need to
### Windows
1. Open a powershell, and initialize Docker Swarm mode:
1. Open a powershell, and initialize Docker Swarm mode:
```shell
docker swarm init
@ -266,13 +266,13 @@ Docker Desktop runs primarily on Docker Engine, which has everything you need to
To add a manager to this swarm, run 'docker swarm join-token manager' and follow the instructions.
```
2. Run a simple Docker service that uses an alpine-based filesystem, and isolates a ping to 8.8.8.8:
2. Run a simple Docker service that uses an alpine-based filesystem, and isolates a ping to 8.8.8.8:
```shell
docker service create --name demo alpine:3.5 ping 8.8.8.8
```
3. Check that your service created one running container:
3. Check that your service created one running container:
```shell
docker service ps demo
@ -285,7 +285,7 @@ Docker Desktop runs primarily on Docker Engine, which has everything you need to
463j2s3y4b5o demo.1 alpine:3.5 docker-desktop Running Running 8 seconds ago
```
4. Check that you get the logs you'd expect for a ping process:
4. Check that you get the logs you'd expect for a ping process:
```shell
docker service logs demo
@ -301,7 +301,7 @@ Docker Desktop runs primarily on Docker Engine, which has everything you need to
...
```
5. Finally, tear down your test service:
5. Finally, tear down your test service:
```shell
docker service rm demo

18
get-started/part3.md
View File

@ -20,15 +20,15 @@ At this point, you've built a containerized application in [Part 2](part2.md) on
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.
1. Visit the Docker Hub sign up page, [https://hub.docker.com/signup](https://hub.docker.com/signup).
1. Visit the Docker Hub sign up page, [https://hub.docker.com/signup](https://hub.docker.com/signup).
2. Fill out the form and submit to create your Docker ID.
2. Fill out the form and submit to create your Docker ID.
3. Verify your email address to complete the registration process.
3. Verify your email address to complete the registration process.
4. Click on the Docker icon in your toolbar or system tray, and click **Sign in / Create Docker ID**.
4. Click on the Docker icon in your toolbar or system tray, and click **Sign in / Create Docker ID**.
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.
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.
> You can do the same thing from the command line by typing `docker login`.
@ -36,19 +36,19 @@ If you don't yet have a Docker ID, follow these steps to set one up; this will a
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.
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.
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.
2. Fill out the repository name as `bulletinboard`. Leave all the other options alone for now, and click **Create** at the bottom.
2. Fill out the repository name as `bulletinboard`. Leave all the other options alone for now, and click **Create** at the bottom.
![make a repo](images/newrepo.png){:width="100%"}
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):
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):
```shell
docker image tag bulletinboard:1.0 gordon/bulletinboard:1.0
```
4. Finally, push your image to Docker Hub:
4. Finally, push your image to Docker Hub:
```shell
docker image push gordon/bulletinboard:1.0

1
get-started/swarm-deploy.md
View File

@ -26,7 +26,6 @@ Swarm never creates individual containers like we did in the previous step of th
Let's write a simple stack file to run and manage our bulletin board. Place the following in a file called `bb-stack.yaml`:
```yaml
version: '3.7'