Files
docker-cli/components/engine/man
Akihiro Suda a880fa14a9 update go-md2man to v1.0.5
Due to the issue of go-md2man, a numbered list in `man docker login` was not rendered correctly.
a8f937e113

Signed-off-by: Akihiro Suda <suda.akihiro@lab.ntt.co.jp>
Upstream-commit: cfe16e0d5b4bb7d1d194553f2a82cc1879d60e6b
Component: engine
2016-06-23 01:58:37 +00:00
..
2015-06-10 13:43:35 -07:00
2016-02-17 11:55:56 +08:00
2015-10-13 11:52:14 -04:00
2016-02-25 09:48:21 +08:00
2016-06-02 17:17:22 +08:00
2015-11-10 09:33:55 +08:00
2016-02-25 09:48:21 +08:00
2015-06-10 13:43:35 -07:00
2015-06-10 13:43:35 -07:00
2015-10-13 11:52:14 -04:00
2015-11-10 09:33:55 +08:00
2016-02-25 09:48:21 +08:00
2016-03-22 08:16:52 +01:00
2015-11-10 09:33:55 +08:00
2015-06-10 13:43:35 -07:00
2016-06-23 01:58:37 +00: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/).