github/wp-docker-buildx
0
0
Fork 0
mirror of https://github.com/thegeeklab/wp-docker-buildx.git synced 2024-11-26 05:30:39 +00:00
Code Issues Releases Activity

Merge pull request #16 from x-cray/patch-1

Browse Source 
Update DOCS to match the latest code [CI SKIP]
This commit is contained in:
Brad Rydzewski 2015-11-27 19:36:42 -08:00
commit 2f245a7577
1 changed files with 11 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
DOCS.md
View File

@ -43,7 +43,7 @@ publish:
Or you may prefer to build an image with multiple tags: Or you may prefer to build an image with multiple tags:
``` ```yaml
publish: publish:
docker: docker:
username: kevinbacon username: kevinbacon
@ -62,7 +62,7 @@ Note that in the above example we quote the version numbers. If the yaml parser
The Drone build environment is, by default, ephemeral meaning that you layers are not saved between builds. The below example combines Drone's caching feature and Docker's `save` and `load` capabilities to cache and restore image layers between builds: The Drone build environment is, by default, ephemeral meaning that you layers are not saved between builds. The below example combines Drone's caching feature and Docker's `save` and `load` capabilities to cache and restore image layers between builds:
``` ```yaml
publish: publish:
docker: docker:
username: kevinbacon username: kevinbacon
@ -74,21 +74,27 @@ publish:
- "1.0.1" - "1.0.1"
load: docker/image.tar load: docker/image.tar
save: save:
file: docker/image.tar destination: docker/image.tar
tags: latest tag: latest
cache: cache:
mount: mount:
- docker/image.tar - docker/image.tar
``` ```
You might also want to create a `.dockerignore` file in your repo to exclude `image.tar` from Docker build context:
```
docker/*
```
In some cases caching will greatly improve build performance, however, the tradeoff is that caching Docker image layers may consume very large amounts of disk space. In some cases caching will greatly improve build performance, however, the tradeoff is that caching Docker image layers may consume very large amounts of disk space.
## Troubleshooting ## Troubleshooting
For detailed output you can set the `DOCKER_LAUNCH_DEBUG` environment variable in your plugin configuration. This starts Docker with verbose logging enabled. For detailed output you can set the `DOCKER_LAUNCH_DEBUG` environment variable in your plugin configuration. This starts Docker with verbose logging enabled.
``` ```yaml
publish: publish:
docker: docker:
environment: environment: