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

Fix more broken links and images

This commit is contained in:
Misty Stanley-Jones 2017-01-26 10:52:00 -08:00
parent 2fb946b8f0
commit 9e29d0e03d
14 changed files with 75 additions and 27 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
_data/toc.yaml
View File

@ -319,7 +319,7 @@ toc:
title: Link via an ambassador container
- sectiontitle: Troubleshoot Docker Engine
section:
- path: /engine/admin/troubleshooting_volume_errors.md
- path: /engine/admin/troubleshooting_volume_errors/
title: Troubleshoot volume problems
- sectiontitle: Manage a swarm
section:
@ -365,7 +365,7 @@ toc:
title: Deploy services to a swarm
- path: /engine/swarm/secrets/
title: Manage sensitive data with Docker secrets
- path: /engine/swarm/swarm_manager_locking.md
- path: /engine/swarm/swarm_manager_locking/
title: Lock your swarm
- path: /engine/swarm/networking/
title: Attach services to an overlay network
@ -449,8 +449,18 @@ toc:
title: docker attach
- path: /engine/reference/commandline/build/
title: docker build
- path: /engine/reference/commandline/checkpoint/
title: docker checkpoint
- sectiontitle: docker checkpoint *
section:
- path: /engine/reference/commandline/checkpoint/
title: docker checkpoint
- path: /engine/reference/commandline/checkpoint_create/
title: docker checkpoint create
- path: /engine/reference/commandline/checkpoint_create/
title: docker checkpoint create
- path: /engine/reference/commandline/checkpoint_ls/
title: docker checkpoint ls
- path: /engine/reference/commandline/checkpoint_rm/
title: docker checkpoint rm
- path: /engine/reference/commandline/commit/
title: docker commit
- sectiontitle: docker container *
@ -1152,7 +1162,7 @@ toc:
- path: /datacenter/ucp/1.1/reference/join/
title: join
- path: /datacenter/ucp/1.1/reference/regen-certs/
title: regen-certs.md
title: regen-certs/
- path: /datacenter/ucp/1.1/reference/restart/
title: restart
- path: /datacenter/ucp/1.1/reference/restore/

2
cs-engine/release-notes/release-notes.md
View File

@ -90,7 +90,7 @@ This release addresses the following issues:
to the local volume driver for nfs mount options.
* [26111](https://github.com/docker/docker/issues/26111) Fix issue with adding
iptables rules due to xtables lock message change.
* [#1572](github.com/docker/libnetwork/issues/1572) Fix daemon panic
* [#1572](https://github.com/docker/libnetwork/issues/1572) Fix daemon panic
* [1130](https://github.com/docker/libnetwork/pull/1130) Fix IPAM out of sync
issue on ungraceful shutdown.

6
docker-for-aws/release-notes.md
View File

@ -21,7 +21,7 @@ Release date: 12/06/2016
- New option to decide if you want to send container logs to CloudWatch. (previously it was always on)
- SSH access has been added to the worker nodes
- The Docker daemon no longer listens on port 2375
- Added a `swarm-exec` to execute a docker command across all of the swarm nodes. See [Executing Docker commands in all swarm nodes](deploy.md#execute-docker-commands-in-all-swarm-nodes) for more details.
- Added a `swarm-exec` to execute a docker command across all of the swarm nodes. See [Executing Docker commands in all swarm nodes](/docker-for-aws/deploy.md#execute-docker-commands-in-all-swarm-nodes) for more details.
## 1.13.0-rc2-beta12
Release date: 11/23/2016
@ -62,8 +62,8 @@ Release date: 10/27/2016
- Docker Engine upgraded to Docker 1.12.3
- Fixed the shell container that runs on the managers, to remove a ssh host key that was accidentally added to the image.
This could have led to a potential man in the middle (MITM) attack. The ssh host key is now generated on host startup, so that each host has its own key.
- The SSH ELB for SSH'ing into the managers has been removed because it is no longer possible to SSH into the managers without getting a security warning
- Each Manager can be SSH'd into by following our deploy [guide](docker-for-aws/deploy.md)
- The SSH ELB for connecting to the managers by SSH has been removed because it is no longer possible to SSH into the managers without getting a security warning
- You can connect to each manager using SSH by following our deploy [guide](/docker-for-aws/deploy.md)
- Added new region us-east-2 (Ohio)
- Fixed some bugs related to upgrading the swarm
- SSH keypair is now a required field in CloudFormation

2
docker-for-azure/release-notes.md
View File

@ -37,7 +37,7 @@ Release date: 11/08/2016
- Docker Engine upgraded to Docker 1.12.3
- Fixed the shell container that runs on the managers, to remove a ssh host key that was accidentally added to the image.
This could have led to a potential man in the middle (MITM) attack. The ssh host key is now generated on host startup, so that each host has its own key.
- The SSH ELB for SSH'ing into the managers has been removed because it is no longer possible to SSH into the managers without getting a security warning
- The SSH ELB for connecting to the managers using SSH has been removed because it is no longer possible to SSH into the managers without getting a security warning
- Multiple managers can be deployed
- All container logs can be found in the `xxxxlog` storage account
- You can connect to each manager using SSH by following our deploy [guide](deploy.md)

2
docker-for-mac/index.md
View File

@ -430,7 +430,7 @@ such as
To activate bash completion, these files need to be copied or symlinked to your
`bash_completion.d/` directory. For example, if you use
[Homebrew](htt://brew.sh/):
[Homebrew](http://brew.sh/):
```bash
ln -s /Applications/Docker.app/Contents/Resources/etc/docker.bash-completion /usr/local/etc/bash_completion.d/docker

2
docker-for-windows/index.md
View File

@ -772,7 +772,7 @@ If you want to go back to using Docker Toolbox, you have to disable the Hyper-V
walkthroughs and source code.
* For a summary of Docker command line interface (CLI) commands, see the
[Docker CLI Reference Guide](/engine/reference/docker.md).
[Docker CLI Reference Guide](/engine/reference/commandline/docker.md).
* Check out the blog post
[Introducing Docker 1.13.0](https://blog.docker.com/2017/01/whats-new-in-docker-1-13/).

13
engine/reference/commandline/checkpoint_create.md Normal file
View File

@ -0,0 +1,13 @@
---
datafolder: engine-cli
datafile: docker_checkpoint_create
title: docker checkpoint create
---
<!--
Sorry, but the contents of this page are automatically generated from
Docker's source code. If you want to suggest a change to the text that appears
here, you'll need to find the string by searching this repo:
https://www.github.com/docker/docker
-->
{% include cli.md %}

13
engine/reference/commandline/checkpoint_ls.md Normal file
View File

@ -0,0 +1,13 @@
---
datafolder: engine-cli
datafile: docker_checkpoint_ls
title: docker checkpoint ls
---
<!--
Sorry, but the contents of this page are automatically generated from
Docker's source code. If you want to suggest a change to the text that appears
here, you'll need to find the string by searching this repo:
https://www.github.com/docker/docker
-->
{% include cli.md %}

13
engine/reference/commandline/checkpoint_rm.md Normal file
View File

@ -0,0 +1,13 @@
---
datafolder: engine-cli
datafile: docker_checkpoint_rm
title: docker checkpoint rm
---
<!--
Sorry, but the contents of this page are automatically generated from
Docker's source code. If you want to suggest a change to the text that appears
here, you'll need to find the string by searching this repo:
https://www.github.com/docker/docker
-->
{% include cli.md %}

2
engine/swarm/admin_guide.md
View File

@ -171,7 +171,7 @@ directory of one of the manager nodes to restore to a new swarm.
You can monitor the health of manager nodes by querying the docker `nodes` API
in JSON format through the `/nodes` HTTP endpoint. Refer to the
[nodes API documentation](/engine/reference/api/docker_remote_api_v1.24.md#36-nodes)
[nodes API documentation](/engine/api/v1.25/#tag/Node)
for more information.
From the command line, run `docker node inspect <id-node>` to query the nodes.

2
engine/swarm/stack-deploy.md
View File

@ -17,7 +17,7 @@ To run through this tutorial, you will need:
1. A Docker Engine of version 1.13.0 or later, running in [swarm
mode](/engine/swarm/swarm-mode.md). If you're not familiar with swarm mode,
you might want to read
[Swarm mode key concepts ](/engine/swarm/how-swarm-mode-works/key-concepts.md)
[Swarm mode key concepts](/engine/swarm/key-concepts.md)
and [How services work](/engine/swarm/how-swarm-mode-works/services.md).
> **Note:** If you're trying things out on a local development environment,

2
engine/userguide/index.md
View File

@ -13,7 +13,7 @@ This guide helps users learn how to use Docker Engine.
- [Hello world in a container](/engine/getstarted/step_one.md)
- [Build your own images](/engine/getstarted/step_four.md)
- [Network containers](/engine/tutorials/networkingcontainers.md)
- [Run a simple application](/engine/userguide/step_three.md)
- [Run a simple application](/engine/getstarted/step_three.md)
- [Manage data in containers](/engine/tutorials/dockervolumes.md)
- [Store images on Docker Hub](/engine/getstarted/step_six.md)

17
opensource/workflow/advanced-contributing.md
View File

@ -15,7 +15,7 @@ Your goal should be to understand the processes described.
At this point, you should have read and worked through the earlier parts of
the project contributor guide. You should also have
<a href="make-a-contribution/" target="_blank"> made at least one project contribution</a>.
[made at least one project contribution](make-a-contribution/){: target="_blank" class="_"}.
## Refactor or cleanup proposal
@ -56,22 +56,21 @@ with someone on design work.
The following provides greater detail on the process:
1. Come up with an idea.
1. Come up with an idea.
Ideas usually come from limitations users feel working with a product. So,
take some time to really use Docker. Try it on different platforms; explore
how it works with different web applications. Go to some community events
and find out what other users want.
2. Review existing issues and proposals to make sure no other user is proposing a similar idea.
2. Review existing issues and proposals to make sure no other user is proposing a similar idea.
The design proposals are <a
href="https://github.com/docker/docker/pulls?q=is%3Aopen+is%3Apr+label%
3Akind%2Fproposal" target="_blank">all online in our GitHub pull requests</a>.
The design proposals are
[all online in our GitHub pull requests](https://github.com/docker/docker/pulls?q=is%3Aopen+is%3Apr+label%3Akind%2Fproposal){: target="_blank" class="_"}
3. Talk to the community about your idea.
3. Talk to the community about your idea.
We have lots of <a href="../../get-help/" target="_blank">community forums</a>
We have lots of [community forums](https://forums.docker.com){: target="_blank" class="_"}
where you can get feedback on your idea. Float your idea in a forum or two
to get some commentary going on it.
@ -149,4 +148,4 @@ Making a pull request with a design proposal simplifies this process:
* as a proposal changes and is updated, pages reset as line items resolve
* GitHub maintains the entire history
While proposals in pull requests do not end up merged into a master repository, they provide a convenient tool for managing the design process.
While proposals in pull requests do not end up merged into a master repository, they provide a convenient tool for managing the design process.

6
swarm/swarm_at_scale/deploy-app.md
View File

@ -16,7 +16,7 @@ starting a number of "Dockerized applications" running in containers.
The diagram below shows the final application configuration including the overlay
container network, `voteapp`.
![](/swarm/swarm_at_scale/images/final-result.png)
![](/swarm/images/final-result.png)
In this procedure you will connect containers to this network. The `voteapp`
network is available to all Docker hosts using the Consul discovery backend.
@ -239,7 +239,7 @@ Now, you can test your application.
You should see something similar to the following:
![](/swarm/swarm_at_scale/images/vote-app-test.png)
![](/swarm/images/vote-app-test.png)
2. Click on one of the two voting options.
3. Navigate to the `http://results.myenterprise.example.com` site to see the results.
@ -247,7 +247,7 @@ Now, you can test your application.
You'll see both sides change as you switch your vote.
![](/swarm/swarm_at_scale/images/votes.gif)
![](/swarm/images/votes.gif)
## Extra Credit: Deployment with Docker Compose