mirror/github.com-tmaier-docker-compose
1
0
Fork 0
mirror of https://github.com/tmaier/docker-compose synced 2024-11-22 16:01:59 +01:00
Code Issues
f7db8c7577
github.com-tmaier-docker-co.../README.md

42 lines
1.5 KiB
Markdown
Raw Normal View History

Add README.md
2017-01-04 01:52:31 +01:00
# Docker Compose
Add badges to README
2017-01-29 14:15:32 +01:00
[![Docker Automated buil](https://img.shields.io/docker/automated/tmaier/docker-compose.svg)](https://hub.docker.com/r/tmaier/docker-compose/)
[![Docker Pulls](https://img.shields.io/docker/pulls/tmaier/docker-compose.svg)](https://hub.docker.com/r/tmaier/docker-compose/)
[![GitHub issues](https://img.shields.io/github/issues/tmaier/docker-compose.svg)](https://github.com/tmaier/docker-compose/issues)
[![GitHub stars](https://img.shields.io/github/stars/tmaier/docker-compose.svg?style=social&label=Star)](https://github.com/tmaier/docker-compose)
Add versions based on different docker versions
2017-01-26 16:56:29 +01:00
This docker image installs docker-compose on top of the `docker` image.
Pin docker-compose versions to the time of release - Otherwise the docker-compose version is the latest available at time of build, which may not be compatible or expected - The latest `COMPOSE_VERSION` can be taken by setting the argument blank (or leaving it as is in the case of `latest`) - pip requires the `.*` to denote that we want the latest patch level, eg. just putting `docker-compose==1.11` installs `1.11.0` instead of `1.11.2` - The extra `${COMPOSE_VERSION:+==}` is because pip errors out with `docker-compose==` Fixes #4
2018-04-18 16:44:10 +02:00
This is very useful for CI pipelines, which leverage "Docker in Docker".
Add versions based on different docker versions
2017-01-26 16:56:29 +01:00
Update README - update versions - add hint to open Github issues or pull requests
2017-09-07 13:22:26 +02:00
## Docker versions supported
There are versions based on different docker versions, e.g. `latest`, `17.06`, `17.03` and `1.13`.
Pin docker-compose versions to the time of release - Otherwise the docker-compose version is the latest available at time of build, which may not be compatible or expected - The latest `COMPOSE_VERSION` can be taken by setting the argument blank (or leaving it as is in the case of `latest`) - pip requires the `.*` to denote that we want the latest patch level, eg. just putting `docker-compose==1.11` installs `1.11.0` instead of `1.11.2` - The extra `${COMPOSE_VERSION:+==}` is because pip errors out with `docker-compose==` Fixes #4
2018-04-18 16:44:10 +02:00
docker-compose matches the latest minor version available when the docker release was made. Eg, `17.06` includes docker-compose 1.15.0. The `latest` tag always includes the latest docker-compose build.
Update README - update versions - add hint to open Github issues or pull requests
2017-09-07 13:22:26 +02:00
Please open an issue or a pull request (preferred) [at GitHub](https://github.com/tmaier/docker-compose), if a version is missing.
Add badges to README
2017-01-29 14:15:32 +01:00
Add simple usage instructions for GitLab CI
2017-10-04 09:48:32 +02:00
## Usage instructions for GitLab CI
You may use it like this in your `.gitlab-ci.yml` file.
```yaml
image: tmaier/docker-compose:latest
services:
- docker:dind
before_script:
- docker info
- docker-compose --version
build image:
stage: build
script:
- docker-compose build
```
Add badges to README
2017-01-29 14:15:32 +01:00
## Author
[Tobias L. Maier](http://tobiasmaier.info) for [BauCloud GmbH](https://www.baucloud.com)
Copy Permalink