Bump io.fabric8:docker-maven-plugin from 0.44.0 to 0.45.0

[dependabot]

Bumps io.fabric8:docker-maven-plugin from 0.44.0 to 0.45.0.

Release notes

Sourced from io.fabric8:docker-maven-plugin's releases.

0.45.0 (2024-07-27)

• Automatically create parent directories of portPropertyFile path (1761)
• Use complete image id in DockerAccessWithHcClient while fetching image id (1764)
• Add skip tag to the image level by <skipTag> (1787)
• Remove usage of AnsiConsole (1791)
• Gracefully handle 404 when removing container (1793)
• Added support for platform attribute of a container in the docker-compose configuration.
• Image Build Config BuildArgs should be passed while pulling images (1756)
• docker:push failed with build ARG in FROM (1778)
• Add the possibility to give secret to buildx build (1798
• FROM can reference ARG that references other ARG (1800)

Thanks to our contributors ❤️ 🤗

• @​kevinleturc
• @​Willena
• @​attiand
• @​nodece
• @​mdxabu
• @​slawekjaranowski
• @​sebastiankirsch

Changelog

Sourced from io.fabric8:docker-maven-plugin's changelog.

ChangeLog

• 0.46-SNAPSHOT:

• 0.45.0 (2024-07-27):

  • Automatically create parent directories of portPropertyFile path (1761)
  • Use complete image id in DockerAccessWithHcClient while fetching image id (1764)
  • Add skip tag to the image level by <skipTag> (1787)
  • Remove usage of AnsiConsole (1791)
  • Gracefully handle 404 when removing container (1793)
  • Added support for platform attribute of a container in the docker-compose configuration.
  • Image Build Config BuildArgs should be passed while pulling images (1756)
  • docker:push failed with build ARG in FROM (1778)
  • Add the possibility to give secret to buildx build (1798
  • FROM can reference ARG that references other ARG (1800)

• 0.44.0 (2024-02-17):

  • Add new option "useDefaultExclusion" for build configuration to handle exclusion of hidden files (1708)
  • The option is now propagated down to the buildx command, if it is set in the section. (1717)
  • Fix Buildx build with Dockerfile outside of the Docker build context directory (1721)
  • Add support setting driverOpts for buildx (1704)
  • Multi-Architecture push is not sending pull registry auth credentials (1709)
  • Adding support for --cacheFrom and --cacheTo buildX arguments (1621)
  • Add support for using maven/system properties for an ARG used as the FROM image in a dockerfile (1731)
  • Revert workaround for checking docker version for checking whether to add docker --config flag or not. (1754)
  • Add a workaround to copy docker-buildx binary to temporary config directory created for docker buildx build. This seems to make docker recognize buildx even after config override. (1754)
  • Fix Windows volume bindings for Rancher, Podman and Windows-based containers (1719)
  • Extract the Docker Compose v2.1+ depends_on conditions and apply them as Docker Maven Plugin waiting configurations (888)
  • Update org.apache.maven:maven-core to 3.8.1 (1702)

• 0.43.4 (2023-08-18):

  • Always pass --config option for latest versions of Docker CLI (1701)

• 0.43.3 (2023-08-13):

  • Only add --config to buildx command string when authentication credentials are coming from outside sources
  • Remove hardcoded --node value while creating buildx builder

• 0.43.2 (2023-07-29):

  • Make --config from buildx command string generation optional (1673) @​robfrank

• 0.43.1 (2023-07-28):

  • Resolve registry auth URL by registry ID (1688) @​wajda
  • Allow 'host-gateway' as non-resolvable hostname in extraHosts (1527) @​azaaiman
  • Bump guava from 31.1-jre to 32.0.1-jre (1686) @​dependabot
  • Bump jib-core from 0.23.0 to 0.24.0 (1686) @​rohanKanojia
  • Fix unauthorized error with buildx needing multiple credentials (1583) @​eocantu
  • Add logger to HTTP ping checker (1689) @​ryanrishi

• 0.43.0 (2023-05-20):

  • Make buildx build single non-native platform if requested (1665) @​martyvona
  • Support for buildx option to disable attestations (1661) @​chonton

... (truncated)

Commits

• c634d9d [RELEASE] Update Project version to v0.45.0
• 50047d0 ci : Add a pipeline for release to maven central
• af3a6d0 ci : Fix documentation deploy pipeline (#1808)
• 3f55e01 feature: Add the possibility to give secret to buildx build (#1798) (#1799)
• 7971f73 fix: arg stated in a FROM clause can reference other args (#1800)
• e980189 fix : RegistryService should also consider buildArgs while resolving base images
• ac5e09a Add IT test
• f4de3af Gracefully handle 404 when removing container
• c1ff71f Remove usage of AnsiConsole
• 150970d Improve test
• Additional commits viewable in compare view

You can trigger a rebase of this PR by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[quarkus-bot]

Status for workflow Quarkus CI

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

✅ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

You can consult the Develocity build scans.

---

Flaky tests - Develocity

⚙️ JVM Tests - JDK 17

📦 integration-tests/opentelemetry

✖ io.quarkus.it.opentelemetry.OpenTelemetryInjectionsTest.testOTelInjections - History

• Condition with Lambda expression in io.quarkus.it.opentelemetry.OpenTelemetryInjectionsTest was not fulfilled within 5 seconds. - org.awaitility.core.ConditionTimeoutException

org.awaitility.core.ConditionTimeoutException: Condition with Lambda expression in io.quarkus.it.opentelemetry.OpenTelemetryInjectionsTest was not fulfilled within 5 seconds.
	at org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:167)
	at org.awaitility.core.CallableCondition.await(CallableCondition.java:78)
	at org.awaitility.core.CallableCondition.await(CallableCondition.java:26)
	at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:1006)
	at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:975)
	at io.quarkus.it.opentelemetry.OpenTelemetryInjectionsTest.reset(OpenTelemetryInjectionsTest.java:26)
	at java.base/java.lang.reflect.Method.invoke(Method.java:568)

---

⚙️ JVM Tests - JDK 21

📦 integration-tests/opentelemetry

✖ io.quarkus.it.opentelemetry.OpenTelemetryInjectionsTest.testOTelInjections - History

• Condition with Lambda expression in io.quarkus.it.opentelemetry.OpenTelemetryInjectionsTest was not fulfilled within 5 seconds. - org.awaitility.core.ConditionTimeoutException

org.awaitility.core.ConditionTimeoutException: Condition with Lambda expression in io.quarkus.it.opentelemetry.OpenTelemetryInjectionsTest was not fulfilled within 5 seconds.
	at org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:167)
	at org.awaitility.core.CallableCondition.await(CallableCondition.java:78)
	at org.awaitility.core.CallableCondition.await(CallableCondition.java:26)
	at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:1006)
	at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:975)
	at io.quarkus.it.opentelemetry.OpenTelemetryInjectionsTest.reset(OpenTelemetryInjectionsTest.java:26)
	at java.base/java.lang.reflect.Method.invoke(Method.java:580)

---

⚙️ Maven Tests - JDK 17

📦 integration-tests/maven

✖ io.quarkus.maven.it.RemoteDevMojoIT.testThatTheApplicationIsReloadedOnNewResource - History

• org.awaitility.core.ConditionTimeoutException: Condition with Lambda expression in io.quarkus.maven.it.RunAndCheckWithAgentMojoTestBase was not fulfilled within 1 minutes. - java.lang.RuntimeException

java.lang.RuntimeException: org.awaitility.core.ConditionTimeoutException: Condition with Lambda expression in io.quarkus.maven.it.RunAndCheckWithAgentMojoTestBase was not fulfilled within 1 minutes.
	at io.quarkus.maven.it.RunAndCheckWithAgentMojoTestBase.runAndCheck(RunAndCheckWithAgentMojoTestBase.java:86)
	at io.quarkus.maven.it.RemoteDevMojoIT.testThatTheApplicationIsReloadedOnNewResource(RemoteDevMojoIT.java:67)
	at java.base/java.lang.reflect.Method.invoke(Method.java:568)
	at java.base/java.util.ArrayList.forEach(ArrayList.java:1511)
	at java.base/java.util.ArrayList.forEach(ArrayList.java:1511)
Caused by: org.awaitility.core.ConditionTimeoutException: Condition with Lambda expression in io.quarkus.maven.it.RunAndCheckWithAgentMojoTestBase was not fulfilled within 1 minutes.
	at org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:167)

✖ io.quarkus.maven.it.RemoteDevMojoIT.testThatTheApplicationIsReloadedOnNewResource - History

• org.awaitility.core.ConditionTimeoutException: Condition with Lambda expression in io.quarkus.maven.it.RunAndCheckWithAgentMojoTestBase was not fulfilled within 1 minutes. - java.lang.RuntimeException

java.lang.RuntimeException: org.awaitility.core.ConditionTimeoutException: Condition with Lambda expression in io.quarkus.maven.it.RunAndCheckWithAgentMojoTestBase was not fulfilled within 1 minutes.
	at io.quarkus.maven.it.RunAndCheckWithAgentMojoTestBase.runAndCheck(RunAndCheckWithAgentMojoTestBase.java:86)
	at io.quarkus.maven.it.RemoteDevMojoIT.testThatTheApplicationIsReloadedOnNewResource(RemoteDevMojoIT.java:67)
	at java.base/java.lang.reflect.Method.invoke(Method.java:568)
	at java.base/java.util.ArrayList.forEach(ArrayList.java:1511)
	at java.base/java.util.ArrayList.forEach(ArrayList.java:1511)
Caused by: org.awaitility.core.ConditionTimeoutException: Condition with Lambda expression in io.quarkus.maven.it.RunAndCheckWithAgentMojoTestBase was not fulfilled within 1 minutes.
	at org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:167)

[gastaldi]

@dependabot merge