Docker-build fails to detect podman

[edeandrea]

Although I can't reproduce #41085 I found some things which may cause it. See the conversation history in #41085.

Fixes #41085

[edeandrea]

FYI this is an addition to #40729, so it'll have to land wherever that lands.

[cescoffier]

Following the reported issue, I would add a warning when the docker extension is used and fallback on podman. Thus we inform the user that using the specific podman extension is better.

Now there are teams where some members use docker and some podman. In this case what happens if we use both extensions?

[edeandrea]

Now there are teams where some members use docker and some podman. In this case what happens if we use both extensions?

If they don't care about doing anything podman-specific (like building multi-arch images) then they can continue doing what they are doing today.

If they want to do things which deviate from common functionality (like building multi-arch images) then they would need both extensions & to configure both extensions, and then use quarkus.container-image.builder=docker|podman to set which one wins.

[edeandrea]

Following the reported issue, I would add a warning when the docker extension is used and fallback on podman. Thus we inform the user that using the specific podman extension is better

@cescoffier this is done. I've rebased my commits into a single commit.

[gsmet]

Not sure what's going on but CI looks stuck on this one. I'll see what I can do.

[quarkus-bot]

Status for workflow Quarkus CI

This is the status report for running Quarkus CI on commit b90b893.

Failing Jobs

Status	Name	Step	Failures	Logs	Raw logs	Build scan

---

Flaky tests - Develocity

⚙️ JVM Tests - JDK 17

📦 extensions/smallrye-reactive-messaging-kafka/deployment

✖ io.quarkus.smallrye.reactivemessaging.kafka.deployment.dev.KafkaDevServicesDevModeTestCase.sseStream - History

• Assertion condition defined as a Lambda expression in io.quarkus.smallrye.reactivemessaging.kafka.deployment.dev.KafkaDevServicesDevModeTestCase Expecting size of: [] to be greater than or equal to 2 but was 0 within 10 seconds. - org.awaitility.core.ConditionTimeoutException

org.awaitility.core.ConditionTimeoutException: 
Assertion condition defined as a Lambda expression in io.quarkus.smallrye.reactivemessaging.kafka.deployment.dev.KafkaDevServicesDevModeTestCase 
Expecting size of:
  []
to be greater than or equal to 2 but was 0 within 10 seconds.
	at org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:167)
	at org.awaitility.core.AssertionCondition.await(AssertionCondition.java:119)
	at org.awaitility.core.AssertionCondition.await(AssertionCondition.java:31)

[ppalaga]

Due to this change, all callers of detectContainerRuntime() will fail with NoSuchMethodException unless they are recompiled. Let me send a PR to get the method back.

[edeandrea]

Yikes! Totally my bad @ppalaga . I can take care of it if you'd like