Files
docker-cli/man
Sven Dowideit 0095e6fc23 Default the tcp port to 2376 if tls is on, and 2375 if not
Refactor so that the Host flag validation doesn't destroy the user's input,
and then post process the flags when we know the TLS options

Signed-off-by: Sven Dowideit <SvenDowideit@home.org.au>
2017-06-02 00:07:12 +00:00
..
2017-06-02 00:07:09 +00:00
2017-06-02 00:06:57 +00:00
2017-06-02 00:07:11 +00:00
2017-06-02 00:06:57 +00:00
2017-06-02 00:07:03 +00:00
2017-06-02 00:06:57 +00:00
2017-06-02 00:06:57 +00:00
2017-06-02 00:07:11 +00:00
2017-06-02 00:07:08 +00:00
2017-06-02 00:06:57 +00:00
2017-06-02 00:07:10 +00:00
2017-06-02 00:07:11 +00:00
2017-06-02 00:07:11 +00:00
2017-06-02 00:07:08 +00:00
2017-06-02 00:06:57 +00:00
2017-06-02 00:07:02 +00:00
2017-06-02 00:06:57 +00: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/).