36 lines
884 B
Markdown
36 lines
884 B
Markdown
|
---
|
||
|
|
layout: "docs"
|
||
|
|
page_title: "docker-save Post-Processor"
|
||
|
|
---
|
||
|
|
|
||
|
|
# Docker Save Post-Processor
|
||
|
|
|
||
|
|
Type: `docker-save`
|
||
|
|
|
||
|
|
The Docker Save post-processor takes an artifact from the
|
||
|
|
[docker builder](/docs/builders/docker.html) that was committed
|
||
|
|
and saves it to a file. This is similar to exporting the Docker image
|
||
|
|
directly from the builder, except that it preserves the hierarchy of
|
||
|
|
images and metadata.
|
||
|
|
|
||
|
|
We understand the terminology can be a bit confusing, but we've
|
||
|
|
adopted the terminology from Docker, so if you're familiar with that, then
|
||
|
|
you'll be familiar with this and vice versa.
|
||
|
|
|
||
|
|
## Configuration
|
||
|
|
|
||
|
|
The configuration for this post-processor is extremely simple.
|
||
|
|
|
||
|
|
* `path` (string) - The path to save the image.
|
||
|
|
|
||
|
|
## Example
|
||
|
|
|
||
|
|
An example is shown below, showing only the post-processor configuration:
|
||
|
|
|
||
|
|
<pre class="prettyprint">
|
||
|
|
{
|
||
|
|
"type": "docker-save",
|
||
|
|
"path": "foo.tar"
|
||
|
|
}
|
||
|
|
</pre>
|