toolshed/docker-cli
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Looking into some broken links, I noticed that we don't need to use

Browse Source 
relative paths, and also fixed some broken images.

There are still more todo - next PR I think :)

Docker-DCO-1.1-Signed-off-by: Sven Dowideit <SvenDowideit@fosiki.com> (github: SvenDowideit)
Upstream-commit: ada86fc5b736d8b3209429c584384fd9974a148a
Component: engine
This commit is contained in:
Sven Dowideit
2014-04-24 22:12:21 +10:00
parent 772ac62a9b
commit b6080f6f5b
42 changed files with 95 additions and 94 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
components/engine/docs/sources/examples/apt-cacher-ng.md
View File

@ -10,7 +10,7 @@ page_keywords: docker, example, package installation, networking, debian, ubuntu
> more information please see [*Check your Docker
> install*](../hello_world/#running-examples).
> - **If you don't like sudo** then see [*Giving non-root
> access*](../../installation/binaries/#dockergroup).
> access*](/installation/binaries/#dockergroup).
> - **If you're using OS X or docker via TCP** then you shouldn't use
> sudo.

2
components/engine/docs/sources/examples/couchdb_data_volumes.md
View File

@ -10,7 +10,7 @@ page_keywords: docker, example, package installation, networking, couchdb, data
> more information please see [*Check your Docker
> install*](../hello_world/#running-examples).
> - **If you don't like sudo** then see [*Giving non-root
> access*](../../installation/binaries/#dockergroup)
> access*](/installation/binaries/#dockergroup)
Here's an example of using data volumes to share the same data between
two CouchDB containers. This could be used for hot upgrades, testing

6
components/engine/docs/sources/examples/hello_world.md
View File

@ -15,7 +15,7 @@ like `/var/lib/docker/repositories: permission denied`
you may have an incomplete Docker installation or insufficient
privileges to access docker on your machine.
Please refer to [*Installation*](../../installation/)
Please refer to [*Installation*](/installation/)
for installation instructions.
## Hello World
@ -26,7 +26,7 @@ for installation instructions.
> more information please see [*Check your Docker
> install*](#check-your-docker-installation).
> - **If you don't like sudo** then see [*Giving non-root
> access*](../../installation/binaries/#dockergroup)
> access*](/installation/binaries/#dockergroup)
This is the most basic example available for using Docker.
@ -71,7 +71,7 @@ See the example in action
> more information please see [*Check your Docker
> install*](#check-your-docker-installation).
> - **If you don't like sudo** then see [*Giving non-root
> access*](../../installation/binaries/#dockergroup)
> access*](/installation/binaries/#dockergroup)
And now for the most boring daemon ever written!

2
components/engine/docs/sources/examples/mongodb.md
View File

@ -10,7 +10,7 @@ page_keywords: docker, example, package installation, networking, mongodb
> more information please see [*Check your Docker
> install*](../hello_world/#running-examples).
> - **If you don't like sudo** then see [*Giving non-root
> access*](../../installation/binaries/#dockergroup)
> access*](/installation/binaries/#dockergroup)
The goal of this example is to show how you can build your own Docker
images with MongoDB pre-installed. We will do that by constructing a

2
components/engine/docs/sources/examples/nodejs_web_app.md
View File

@ -10,7 +10,7 @@ page_keywords: docker, example, package installation, node, centos
> more information please see [*Check your Docker
> install*](../hello_world/#running-examples).
> - **If you don't like sudo** then see [*Giving non-root
> access*](../../installation/binaries/#dockergroup)
> access*](/installation/binaries/#dockergroup)
The goal of this example is to show you how you can build your own
Docker images from a parent image using a `Dockerfile`

4
components/engine/docs/sources/examples/postgresql_service.md
View File

@ -10,7 +10,7 @@ page_keywords: docker, example, package installation, postgresql
> more information please see [*Check your Docker
> install*](../hello_world/#running-examples).
> - **If you don't like sudo** then see [*Giving non-root
> access*](../../installation/binaries/#dockergroup)
> access*](/installation/binaries/#dockergroup)
## Installing PostgreSQL on Docker
@ -87,7 +87,7 @@ And run the PostgreSQL server container (in the foreground):
$ sudo docker run -rm -P -name pg_test eg_postgresql
There are 2 ways to connect to the PostgreSQL server. We can use [*Link
Containers*](../../use/working_with_links_names/#working-with-links-names),
Containers*](/use/working_with_links_names/#working-with-links-names),
or we can access it from our host (or the network).
> **Note**:

2
components/engine/docs/sources/examples/python_web_app.md
View File

@ -10,7 +10,7 @@ page_keywords: docker, example, python, web app
> more information please see [*Check your Docker
> install*](../hello_world/#running-examples).
> - **If you don't like sudo** then see [*Giving non-root
> access*](../../installation/binaries/#dockergroup)
> access*](/installation/binaries/#dockergroup)
While using Dockerfiles is the preferred way to create maintainable and
repeatable images, its useful to know how you can try things out and

2
components/engine/docs/sources/examples/running_redis_service.md
View File

@ -10,7 +10,7 @@ page_keywords: docker, example, package installation, networking, redis
> more information please see [*Check your Docker
> install*](../hello_world/#running-examples).
> - **If you don't like sudo** then see [*Giving non-root
> access*](../../installation/binaries/#dockergroup)
> access*](/installation/binaries/#dockergroup)
Very simple, no frills, Redis service attached to a web application
using a link.

2
components/engine/docs/sources/examples/running_riak_service.md
View File

@ -10,7 +10,7 @@ page_keywords: docker, example, package installation, networking, riak
> more information please see [*Check your Docker
> install*](../hello_world/#running-examples).
> - **If you don't like sudo** then see [*Giving non-root
> access*](../../installation/binaries/#dockergroup)
> access*](/installation/binaries/#dockergroup)
The goal of this example is to show you how to build a Docker image with
Riak pre-installed.

2
components/engine/docs/sources/examples/running_ssh_service.md
View File

@ -9,7 +9,7 @@ page_keywords: docker, example, package installation, networking
> more information please see [*Check your Docker
> install*](../hello_world/#running-examples).
> - **If you don't like sudo** then see [*Giving non-root
> access*](../../installation/binaries/#dockergroup)
> access*](/installation/binaries/#dockergroup)
The following Dockerfile sets up an sshd service in a container that you
can use to connect to and inspect other container's volumes, or to get

2
components/engine/docs/sources/examples/using_supervisord.md
View File

@ -10,7 +10,7 @@ page_keywords: docker, supervisor, process management
> more information please see [*Check your Docker
> install*](../hello_world/#running-examples).
> - **If you don't like sudo** then see [*Giving non-root
> access*](../../installation/binaries/#dockergroup)
> access*](/installation/binaries/#dockergroup)
Traditionally a Docker container runs a single process when it is
launched, for example an Apache daemon or a SSH server daemon. Often