podman/test/compose
Paul Holzinger 2f5025a2d7
compat API: allow MacAddress on container config
docker-compose sets the mac address in the container config and not the
network endpoint config. This is ugly when you have more than one
network, in this case docker just chooses the first network.

Fixes #16411

Signed-off-by: Paul Holzinger <pholzing@redhat.com>
2022-12-05 16:52:36 +01:00
..
disable_healthcheck Docker-compose disable healthcheck properly handled 2022-07-05 08:02:22 -04:00
env_and_volume add compose test descriptions 2020-12-11 10:07:13 -06:00
images add compose test descriptions 2020-12-11 10:07:13 -06:00
ipam_set_ip compat API: allow MacAddress on container config 2022-12-05 16:52:36 +01:00
mount_and_label Fix AVC denials in tests of volume mounts 2021-08-18 12:04:06 -04:00
port_map_diff_port add compose test descriptions 2020-12-11 10:07:13 -06:00
simple_port_map add compose test descriptions 2020-12-11 10:07:13 -06:00
slirp4netns_opts fix compose test error in retry logic 2022-03-22 15:22:17 +01:00
two_networks Set names in compose tests based on version 2022-03-17 15:16:13 -04:00
update_network_mtu (rootful) docker-compose now updates network MTU 2022-07-05 07:54:09 -04:00
uptwice compat API: network inspect do not show isolate option 2022-09-25 22:10:22 -04:00
README.md test-compose: rewrite to new subdir form 2020-12-11 09:27:42 -06:00
setup.sh.example add compose test descriptions 2020-12-11 10:07:13 -06:00
teardown.sh.example add compose test descriptions 2020-12-11 10:07:13 -06:00
test-compose Cleanup: fix problems reported by shell lint 2022-09-15 20:10:34 -06:00

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