Ian Wienand 0601df0049 Fix and/or matching for image pre-conditions ...

These matches look like they should be "or" (if any of these images is
already there, fail), not "and".  This caused some confusion when the
image was being leaked (I722ba599fbc690d6cb967070c05215b98a73dcaf) as
this wasn't triggering.

Change-Id: Ic6dad7bbf9013e994eb80a54bc5191a96bd4be94

2022-03-04 06:45:21 +11:00

..

conf

Disable namespacing

2019-10-21 09:47:41 -07:00

files

Disable namespacing

2019-10-21 09:47:41 -07:00

restricted

Add a restricted mode (read authentication required)

2021-07-06 17:46:13 -07:00

cleanup.yaml

Add podman buildset test

2019-10-10 16:49:37 -07:00

docker-buildset.yaml

Fix and/or matching for image pre-conditions

2022-03-04 06:45:21 +11:00

docker-compose.yaml

Disable namespacing

2019-10-21 09:47:41 -07:00

docker.yaml

Add more robust testing of the registry

2022-02-28 14:19:03 -08:00

localtest.yaml

Add podman buildset test

2019-10-10 16:49:37 -07:00

podman-buildset.yaml

Fix and/or matching for image pre-conditions

2022-03-04 06:45:21 +11:00

podman.yaml

podman: make sure we remove the pulled image

2022-03-04 06:45:21 +11:00

post.yaml

Switch to collect-container-logs

2020-01-09 19:42:49 -05:00

restricted.yaml

Add more robust testing of the registry

2022-02-28 14:19:03 -08:00

run.yaml

Merge "Add more robust testing of the registry"

2022-03-03 17:51:21 +00:00

setup.yaml

Add more robust testing of the registry

2022-02-28 14:19:03 -08:00