github.com/marksheahan/packer@v0.10.2-0.20160613200515-1acb2d6645a0/website/source/docs/post-processors/docker-import.html.md (about)

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