This repo will contain docker images
Current versions available:
.
├── 0.4.0
│ └── alpine
│ └── Dockerfile
├── 1.1.0
│ └── debian
│ └── Dockerfile
Images can be found on https://hub.docker.com/r/philipssoftware/bats/.
docker run -it --rm philipssoftware/bats:0.4.0: bats --version
The images obviously contain bats, but also two other files:
REPOTAGS
This file has a url to the REPO with specific commit-sha of the build. Example:
$ docker run -it --rm philipssoftware/bats:0.4.0 cat REPO
https://github.com/philips-software/docker-bats/tree/36ea34634d022e26d87d3e6b3e0f0d2841327e00
This contains all the simular tags at the point of creation.
$ docker run -it --rm philipssoftware/bats:0.4.0 cat TAGS
bats:0.4.0 bats:0.4.0-alpine bats:0.4.0-rc2
You can use this to pin down a version of the container from an existing development build for production. When using bats:10-jdk for development. This ensures that you've got all security updates in your build. If you want to pin the version of your image down for production, you can use this file inside of the container to look for the most specific tag, the last one.
bats:0.4.0,bats:0.4.0-alpine,bats:0.4.0-rc20.4.0/alpine/Dockerfilebats,bats:1.1.0,bats:1.1.0-debian1.1.0/debian/Dockerfile
Why do we have our own docker image definitions?
We often need bats to test our scripts. There is no official docker image, so let's make a version for our build pipelines.
- If you have an issue: report it on the issue tracker
- Jeroen Knoops [email protected]
- Heijden, Remco van der [email protected]
License is MIT. See LICENSE file
This module is part of the Philips Forest.
___ _
/ __\__ _ __ ___ ___| |_
/ _\/ _ \| '__/ _ \/ __| __|
/ / | (_) | | | __/\__ \ |_
\/ \___/|_| \___||___/\__|
Infrastructure
Talk to the forestkeepers in the docker-images-channel on Slack.