We are silently skipping tests that require Docker/podman resulting in a pass, however, podman/Docker is truly a dependency of running the test suite completely (just like Maven or JDK is).

The problem is with using concepts like @DockerRequired, which just skips when docker/podman fails to respond. That happens frequently, when the containerization software is broken or simply not started (especially on macOS/Windows).

If podman/Docker is somehow unsupportable in a given environment, there should be an explicit "opt out" flag, rather than container-based tests being "opt in" by default.