e596b17fbe
**podman compose** is a thin wrapper around an external compose provider such as docker-compose or podman-compose. This means that `podman compose` is executing another tool that implements the compose functionality but sets up the environment in a way to let the compose provider communicate transparently with the local Podman socket. The specified options as well the command and argument are passed directly to the compose provider. The default compose providers are `docker-compose` and `podman-compose`. If installed, `docker-compose` takes precedence since it is the original implementation of the Compose specification and is widely used on the supported platforms (i.e., Linux, Mac OS, Windows). If you want to change the default behavior or have a custom installation path for your provider of choice, please change the `compose_provider` field in `containers.conf(5)`. You may also set the `PODMAN_COMPOSE_PROVIDER` environment variable. Signed-off-by: Valentin Rothberg <vrothberg@redhat.com> |
||
|---|---|---|
| .. | ||
| disable_healthcheck | ||
| env_and_volume | ||
| images | ||
| ipam_set_ip | ||
| mount_and_label | ||
| port_map_diff_port | ||
| simple_port_map | ||
| slirp4netns_opts | ||
| two_networks | ||
| update_network_mtu | ||
| uptwice | ||
| README.md | ||
| setup.sh.example | ||
| teardown.sh.example | ||
| test-compose | ||
README.md
Tests for docker-compose
This directory contains tests for docker-compose under podman.
Each subdirectory must contain one docker-compose.yml file along with all necessary infrastructure for it (e.g. Containerfile, any files to be copied into the container, and so on.
The test-compose script will, for each test subdirectory:
- set up a fresh podman root under an empty working directory;
- run a podman server rooted therein;
- cd to the test subdirectory, and run
docker-compose up -d; - source
tests.sh; - run
docker-compose down.
As a special case, setup.sh and teardown.sh in the test directory
will contain commands to be executed prior to docker-compose up and
after docker-compose down respectively.
tests.sh will probably contain commands of the form
test_port 12345 = 'hello there'
Where 12345 is the port to curl to; '=' checks equality, '~' uses expr
to check substrings; and 'hello there' is a string to look for in
the curl results.
Usage:
$ sudo test/compose/test-compose [pattern]
By default, all subdirs will be run. If given a pattern, only those subdirectories matching 'pattern' will be run.
If $COMPOSE_WAIT is set, test-compose will pause before running
docker-compose down. This can be helpful for you to debug failing tests:
$ env COMPOSE_WAIT=1 sudo --preserve-env=COMPOSE_WAIT test/compose/test-compose
Then, in another window,
# ls -lt /var/tmp/
# X=/var/tmp/test-compose.tmp.XXXXXX <--- most recent results of above
# podman --root $X/root --runroot $X/runroot ps -a
# podman --root $X/root --runroot $X/runroot logs -l