-
-
Save Enteee/fdbb5793ab77f0dc10b76a45cc49716e to your computer and use it in GitHub Desktop.
A `docker-compose` wrapper for multiple configuration files with relative paths
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
#!/usr/bin/env bash | |
# Docker compose wrapper with submodule support | |
# Reads all docker-compose.yaml files given with -f / --files and compiles one | |
# big docker-compose.yaml file before running docker-compose. | |
# | |
# This is useful when you have nested docker-compose subprojects in different | |
# folders which contain relative paths. | |
# see: https://github.com/docker/compose/issues/3874 | |
# | |
# Environment: | |
# - DOCKER_COMPOSE_CONFIG_VERSION: The docker-compose,yaml config file version, default: 2.1 | |
# | |
# Requires: | |
# - sponge (from moreutils https://joeyh.name/code/moreutils/) | |
# - docker & docker-compose | |
# | |
set -euo pipefail | |
PWD="$(pwd)" | |
TMP_FILE="${PWD}/docker-compose-generated.$$.yaml" | |
DOCKER_COMPOSE_CONFIG_VERSION="${DOCKER_COMPOSE_CONFIG_VERSION:-2.1}" | |
finish() { | |
rm "${TMP_FILE}" 2>/dev/null | |
} | |
trap finish EXIT | |
compose-config() { | |
local dir="$(dirname "${1}")" | |
local file="$(basename "${1}")" | |
docker-compose -f "${1}" -f "${TMP_FILE}" config \ | |
| sponge "${TMP_FILE}" | |
} | |
args=() | |
files=() | |
verbose=false | |
while [[ $# -gt 0 ]]; do | |
case "${1}" in | |
-f|--file) | |
shift | |
files+=("${1}") && shift | |
;; | |
--verbose) | |
verbose=true | |
args+=("${1}") && shift | |
;; | |
*) | |
args+=("${1}") && shift | |
;; | |
esac | |
done | |
if [ "${verbose}" == true ]; then | |
set -x | |
fi | |
echo "version: \"${DOCKER_COMPOSE_CONFIG_VERSION}\"" > ${TMP_FILE} | |
for f in ${files[@]}; do | |
compose-config "${f}" | |
done | |
docker-compose -f "${TMP_FILE}" ${args[@]} |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment