Files
docker-cli/components/engine/man
Evan Allrich 2f283a92ed Adding --format= flag
Signed-off-by: Evan Allrich <evan@unguku.com>
Upstream-commit: 78ba5d58e6280f879fa45dd4c73f8284dd4ec031
Component: engine
2016-02-06 09:39:20 -06:00
..
2015-12-30 09:23:35 +08:00
2015-11-21 00:36:56 +08:00
2015-06-10 13:43:35 -07:00
2015-10-13 11:52:14 -04:00
2016-02-02 12:28:33 +00:00
2015-10-13 11:52:14 -04:00
2016-02-06 09:39:20 -06:00
2015-11-10 09:33:55 +08:00
2016-02-02 12:28:33 +00:00
2015-06-10 13:43:35 -07:00
2015-06-10 13:43:35 -07:00
2016-02-02 12:28:33 +00:00
2015-10-13 11:52:14 -04:00
2015-11-10 09:33:55 +08:00
2016-02-02 18:06:09 +01:00
2015-06-10 13:43:35 -07:00
2015-11-10 09:33:55 +08:00
2015-11-10 09:33:55 +08:00
2015-11-10 09:33:55 +08:00
2015-06-10 13:43:35 -07:00
2015-07-21 10:42:02 -04:00
2015-06-10 13:43:35 -07:00

Docker Documentation

This directory contains the Docker user manual in the Markdown format. Do not edit the man pages in the man1 directory. Instead, amend the Markdown (*.md) files.

Generating man pages from the Markdown files

The recommended approach for generating the man pages is via a Docker container using the supplied Dockerfile to create an image with the correct environment. This uses go-md2man, a pure Go Markdown to man page generator.

Building the md2man image

There is a Dockerfile provided in the /man directory of your 'docker/docker' fork.

Using this Dockerfile, create a Docker image tagged docker/md2man:

docker build -t docker/md2man .

Utilizing the image

From within the /man directory run the following command:

docker run -v $(pwd):/man -w /man -i docker/md2man ./md2man-all.sh

The md2man Docker container will process the Markdown files and generate the man pages inside the /man/man1 directory of your fork using Docker volumes. For more information on Docker volumes see the man page for docker run and also look at the article [Sharing Directories via Volumes] (https://docs.docker.com/use/working_with_volumes/).