1
0
Fork 0
mirror of https://github.com/moby/moby.git synced 2022-11-09 12:21:53 -05:00
moby--moby/contrib/man/md
Dan Walsh e625bad3d7 Fix docker man page to reference selinux-enable flag
Docker-DCO-1.1-Signed-off-by: Daniel Walsh <dwalsh@redhat.com> (github: rhatdan)
2014-05-05 08:41:21 -04:00
..
docker-attach.1.md Update contributed man page file names and compilation script for the eventual possibility of non-man1 man pages (hopefully a Dockerfile.5.md, for example) 2014-04-22 06:43:08 -06:00
docker-build.1.md Fixed some missing ']' and the TAG 2014-04-22 22:35:59 -06:00
docker-commit.1.md Update contributed man page file names and compilation script for the eventual possibility of non-man1 man pages (hopefully a Dockerfile.5.md, for example) 2014-04-22 06:43:08 -06:00
docker-cp.1.md Update contributed man page file names and compilation script for the eventual possibility of non-man1 man pages (hopefully a Dockerfile.5.md, for example) 2014-04-22 06:43:08 -06:00
docker-diff.1.md Update contributed man page file names and compilation script for the eventual possibility of non-man1 man pages (hopefully a Dockerfile.5.md, for example) 2014-04-22 06:43:08 -06:00
docker-events.1.md Update contributed man page file names and compilation script for the eventual possibility of non-man1 man pages (hopefully a Dockerfile.5.md, for example) 2014-04-22 06:43:08 -06:00
docker-export.1.md Update contributed man page file names and compilation script for the eventual possibility of non-man1 man pages (hopefully a Dockerfile.5.md, for example) 2014-04-22 06:43:08 -06:00
docker-history.1.md Update contributed man page file names and compilation script for the eventual possibility of non-man1 man pages (hopefully a Dockerfile.5.md, for example) 2014-04-22 06:43:08 -06:00
docker-images.1.md Update contributed man page file names and compilation script for the eventual possibility of non-man1 man pages (hopefully a Dockerfile.5.md, for example) 2014-04-22 06:43:08 -06:00
docker-import.1.md Update contributed man page file names and compilation script for the eventual possibility of non-man1 man pages (hopefully a Dockerfile.5.md, for example) 2014-04-22 06:43:08 -06:00
docker-info.1.md Update contributed man page file names and compilation script for the eventual possibility of non-man1 man pages (hopefully a Dockerfile.5.md, for example) 2014-04-22 06:43:08 -06:00
docker-inspect.1.md Update contributed man page file names and compilation script for the eventual possibility of non-man1 man pages (hopefully a Dockerfile.5.md, for example) 2014-04-22 06:43:08 -06:00
docker-kill.1.md Update contributed man page file names and compilation script for the eventual possibility of non-man1 man pages (hopefully a Dockerfile.5.md, for example) 2014-04-22 06:43:08 -06:00
docker-load.1.md Update contributed man page file names and compilation script for the eventual possibility of non-man1 man pages (hopefully a Dockerfile.5.md, for example) 2014-04-22 06:43:08 -06:00
docker-login.1.md Update contributed man page file names and compilation script for the eventual possibility of non-man1 man pages (hopefully a Dockerfile.5.md, for example) 2014-04-22 06:43:08 -06:00
docker-logs.1.md Update contributed man page file names and compilation script for the eventual possibility of non-man1 man pages (hopefully a Dockerfile.5.md, for example) 2014-04-22 06:43:08 -06:00
docker-port.1.md Update contributed man page file names and compilation script for the eventual possibility of non-man1 man pages (hopefully a Dockerfile.5.md, for example) 2014-04-22 06:43:08 -06:00
docker-ps.1.md Update contributed man page file names and compilation script for the eventual possibility of non-man1 man pages (hopefully a Dockerfile.5.md, for example) 2014-04-22 06:43:08 -06:00
docker-pull.1.md Update contributed man page file names and compilation script for the eventual possibility of non-man1 man pages (hopefully a Dockerfile.5.md, for example) 2014-04-22 06:43:08 -06:00
docker-push.1.md Update contributed man page file names and compilation script for the eventual possibility of non-man1 man pages (hopefully a Dockerfile.5.md, for example) 2014-04-22 06:43:08 -06:00
docker-restart.1.md Update contributed man page file names and compilation script for the eventual possibility of non-man1 man pages (hopefully a Dockerfile.5.md, for example) 2014-04-22 06:43:08 -06:00
docker-rm.1.md Update contributed man page file names and compilation script for the eventual possibility of non-man1 man pages (hopefully a Dockerfile.5.md, for example) 2014-04-22 06:43:08 -06:00
docker-rmi.1.md Update contributed man page file names and compilation script for the eventual possibility of non-man1 man pages (hopefully a Dockerfile.5.md, for example) 2014-04-22 06:43:08 -06:00
docker-run.1.md Update contributed man page file names and compilation script for the eventual possibility of non-man1 man pages (hopefully a Dockerfile.5.md, for example) 2014-04-22 06:43:08 -06:00
docker-save.1.md Update contributed man page file names and compilation script for the eventual possibility of non-man1 man pages (hopefully a Dockerfile.5.md, for example) 2014-04-22 06:43:08 -06:00
docker-search.1.md Update contributed man page file names and compilation script for the eventual possibility of non-man1 man pages (hopefully a Dockerfile.5.md, for example) 2014-04-22 06:43:08 -06:00
docker-start.1.md Update contributed man page file names and compilation script for the eventual possibility of non-man1 man pages (hopefully a Dockerfile.5.md, for example) 2014-04-22 06:43:08 -06:00
docker-stop.1.md Update contributed man page file names and compilation script for the eventual possibility of non-man1 man pages (hopefully a Dockerfile.5.md, for example) 2014-04-22 06:43:08 -06:00
docker-tag.1.md Update contributed man page file names and compilation script for the eventual possibility of non-man1 man pages (hopefully a Dockerfile.5.md, for example) 2014-04-22 06:43:08 -06:00
docker-top.1.md Update contributed man page file names and compilation script for the eventual possibility of non-man1 man pages (hopefully a Dockerfile.5.md, for example) 2014-04-22 06:43:08 -06:00
docker-wait.1.md Update contributed man page file names and compilation script for the eventual possibility of non-man1 man pages (hopefully a Dockerfile.5.md, for example) 2014-04-22 06:43:08 -06:00
docker.1.md Fix docker man page to reference selinux-enable flag 2014-05-05 08:41:21 -04:00
Dockerfile Added a tag to FROM fedora (fedora:20) 2014-04-21 10:42:46 -07:00
md2man-all.sh Update contributed man page file names and compilation script for the eventual possibility of non-man1 man pages (hopefully a Dockerfile.5.md, for example) 2014-04-22 06:43:08 -06:00
README.md Changed Image to image. 2014-04-21 14:37:08 -06: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.

File List

docker.md
docker-attach.md
docker-build.md
docker-commit.md
docker-cp.md
docker-diff.md
docker-events.md
docker-export.md
docker-history.md
docker-images.md
docker-import.md
docker-info.md
docker-inspect.md
docker-kill.md
docker-load.md
docker-login.md
docker-logs.md
docker-port.md
docker-ps.md
docker-pull.md
docker-push.md
docker-restart.md
docker-rmi.md
docker-rm.md
docker-run.md
docker-save.md
docker-search.md
docker-start.md
docker-stop.md
docker-tag.md
docker-top.md
docker-wait.md
Dockerfile
md2man-all.sh

Generating man pages from the Markdown files

The recommended approach for generating the man pages is via a Docker container. Using the supplied Dockerfile, Docker will create a Fedora based container and isolate the Pandoc installation. This is a seamless process, saving you from dealing with Pandoc and dependencies on your own computer.

Building the Fedora / Pandoc image

There is a Dockerfile provided in the docker/contrib/man/md directory.

Using this Dockerfile, create a Docker image tagged fedora/pandoc:

docker build  -t fedora/pandoc .

Utilizing the Fedora / Pandoc image

Once the image is built, run a container using the image with volumes:

docker run -v /<path-to-git-dir>/docker/contrib/man:/pandoc:rw \
-w /pandoc -i fedora/pandoc /pandoc/md/md2man-all.sh

The Pandoc Docker container will process the Markdown files and generate the man pages inside the docker/contrib/man/man1 directory 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] (http://docs.docker.io/use/working_with_volumes/).