github.com/aspring/packer@v0.8.1-0.20150629211158-9db281ac0f89/website/source/docs/post-processors/docker-tag.html.markdown (about) 1 --- 2 layout: "docs" 3 page_title: "docker-tag Post-Processor" 4 description: |- 5 The Packer Docker Tag post-processor takes an artifact from the docker builder that was committed and tags it into a repository. This allows you to use the other Docker post-processors such as docker-push to push the image to a registry. 6 --- 7 8 # Docker Tag Post-Processor 9 10 Type: `docker-tag` 11 12 The Packer Docker Tag post-processor takes an artifact from the 13 [docker builder](/docs/builders/docker.html) that was committed 14 and tags it into a repository. This allows you to use the other 15 Docker post-processors such as 16 [docker-push](/docs/post-processors/docker-push.html) to push the image 17 to a registry. 18 19 This is very similar to the [docker-import](/docs/post-processors/docker-import.html) 20 post-processor except that this works with committed resources, rather 21 than exported. 22 23 ## Configuration 24 25 The configuration for this post-processor is extremely simple. At least 26 a repository is required. 27 28 * `repository` (string) - The repository of the image. 29 30 * `tag` (string) - The tag for the image. By default this is not 31 set. 32 33 ## Example 34 35 An example is shown below, showing only the post-processor configuration: 36 37 ```javascript 38 { 39 "type": "docker-tag", 40 "repository": "mitchellh/packer", 41 "tag": "0.7" 42 } 43 ``` 44 45 This example would take the image created by the Docker builder 46 and tag it into the local Docker process with a name of `mitchellh/packer:0.7`. 47 48 Following this, you can use the 49 [docker-push](/docs/post-processors/docker-push.html) 50 post-processor to push it to a registry, if you want.