Add rootless podman support

[SoMuchForSubtlety]

Follow-up for #5822 with a new CI check for podman.

Open Issues

• pulling from local http registry does not work (see Allow pulling from HTTP registries when using the docker compat API containers/podman#16486)
  • ImagePullPolicyTest::pullsByDefault
  • ImagePullPolicyTest::shouldAlwaysPull
  • ImagePullPolicyTest::shouldSupportCustomPolicies
  • ImagePullPolicyTest::shouldCheckPolicy
  • AmbiguousImagePullTest::testNotUsingParse
  • DockerClientFactoryTest::runCommandInsideDockerShouldNotFailIfImageDoesNotExistsLocally
  • AuthenticatedImagePullTest::testThatAuthLocatorIsUsedForDockerfileBuild
  • AuthenticatedImagePullTest::testThatAuthLocatorIsUsedForContainerCreation
• Port bindings in inspect response are slightly different (see api: remove unmapped ports from PortBindings containers/podman#16818)
  • GenericContainerTest::shouldOnlyPublishExposedPorts
• Network modes host and none don't create network entries (see [Bug]: network modes none and host should create entries in NetworkSettings.Networks containers/podman#17385)
  • DockerNetworkModeTest

[eddumelendez]

@SoMuchForSubtlety thanks again for submitting a PR! However, Podman support should not alter the current tests.

[SoMuchForSubtlety]

@SoMuchForSubtlety thanks again for submitting a PR! However, Podman support should not alter the current tests.

I reverted the test changes and skip them instead.

[SoMuchForSubtlety]

I'll try to get the outstanding compatibility issues fixed in podman. I would be grateful if this PR could stay open to track the progress.

Would it be OK to fix a (probable) bug in the tests?

testcontainers-java/core/src/test/java/org/testcontainers/DockerRegistryContainer.java

Lines 102 to 103 in 98ddbb8

	// push the image to the registry
	client.tagImageCmd(dummyImageId, imageName.asCanonicalNameString(), tag).exec();

imageName.asCanonicalNameString() returns the image name with the tag, so for example localhost:123/my-image:1.0.0, but tagImageCmd takes the image tag as a separate parameter, so the end result would be localhost:123/my-image:1.0.0:1.0.0.
This should probably be client.tagImageCmd(dummyImageId, imageName.getUnversionedPart(), tag).exec();.

According to the docker API spec, the repo parameter should not contain a tag.

[kiview]

Thanks a lot for your work on this PR and your openness to collaboration @SoMuchForSubtlety, this is much appreciated. We can of course keep the PR open to track the progress.

Regarding:

Would it be OK to fix a (probable) bug in the tests?

Of course, maybe even better as a small distinct PR, to decouple it from the Podman development work (since it is indeed independent of it).

[SoMuchForSubtlety]

Podman 4.5.0 with the last required fix landed today, this is ready for review 🙂

[pan3793]

Does it work w/ docker compose?

[SoMuchForSubtlety]

Does it work w/ docker compose?

No, because testcontainers currently uses the deprecated link feature for the compose ambassador container. If/when the implementation is changed to not use links, it should work, but that is out of scope for this PR.

[pan3793]

Got it, thanks @SoMuchForSubtlety

[SoMuchForSubtlety]

This PR has been ready for a while now, any chance of getting a review?

[eddumelendez]

Hi, thanks for the contribution. Our docs provides references to how to configure Testcontainers with other container runtimes already. Due to the existing list of issues related to podman, I am afraid we can not merge this PR. Container runtimes must be compatible with Docker APIs.

[SoMuchForSubtlety]

This PR passes all tests with podman. What are your concerns?