From 0993f24fcf43748d37e0c1743b3caf14fe2ec60c Mon Sep 17 00:00:00 2001 From: James Turnbull Date: Mon, 5 Jun 2017 00:32:59 -0400 Subject: [PATCH] Minor updates to the Docker builder docs to clarify Docker support --- website/source/docs/builders/docker.html.md | 12 +++++------- 1 file changed, 5 insertions(+), 7 deletions(-) diff --git a/website/source/docs/builders/docker.html.md b/website/source/docs/builders/docker.html.md index ecfada932..fc39422dd 100644 --- a/website/source/docs/builders/docker.html.md +++ b/website/source/docs/builders/docker.html.md @@ -17,18 +17,16 @@ Docker. The builder starts a Docker container, runs provisioners within this container, then exports the container for reuse or commits the image. Packer builds Docker containers *without* the use of -[Dockerfiles](https://docs.docker.com/reference/builder/). By not using -Dockerfiles, Packer is able to provision containers with portable scripts or +[Dockerfiles](https://docs.docker.com/engine/reference/builder/). By not using +`Dockerfiles`, Packer is able to provision containers with portable scripts or configuration management systems that are not tied to Docker in any way. It also -has a simpler mental model: you provision containers much the same way you +has a simple mental model: you provision containers much the same way you provision a normal virtualized or dedicated server. For more information, read the section on [Dockerfiles](#dockerfiles). The Docker builder must run on a machine that has Docker installed. Therefore -the builder only works on machines that support Docker (modern Linux machines). -If you want to use Packer to build Docker containers on another platform, use -[Vagrant](https://www.vagrantup.com) to start a Linux environment, then run -Packer within that environment. +the builder only works on machines that support Docker. You can learn about +what [platforms Docker supports and how to install onto them](https://docs.docker.com/engine/installation/) in the Docker documentation. ## Basic Example: Export