iSharkFly-Docs
/
packer-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Add section on importing docker container artifacts

This commit is contained in:
b 2013-12-24 17:40:13 -08:00
parent d569573923
commit 93af1bf81d
1 changed files with 10 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
website/source/docs/builders/docker.html.markdown
View File

@ -58,6 +58,16 @@ Optional:
`docker pull` prior to use. Otherwise, it is assumed the image already `docker pull` prior to use. Otherwise, it is assumed the image already
exists and can be used. This defaults to true if not set. exists and can be used. This defaults to true if not set.
## Using the generated artifact
Once the tar artifact has been generated, you will likely want to import, tag, and push it to a container repository.Until packer supports management of the docker image metadata, this process is manual. For example, the following will import mycontainer-123456789.tar as the repository registry.mydomain.com/mycontainer, tagged with 'latest':
<pre class="prettyprint">
sudo docker import - registry.mydomain.com/mycontainer:latest < mycontainer-123456789.tar
</pre>
You can then add additional tags and push the image as usual with docker tag and docker push, respectively.
## Dockerfiles ## Dockerfiles
This builder allows you to build Docker images _without_ Dockerfiles. This builder allows you to build Docker images _without_ Dockerfiles.