Bump docker-maven-plugin from 0.40.3 to 0.41.0

[dependabot]

Bumps docker-maven-plugin from 0.40.3 to 0.41.0.

Release notes

Sourced from docker-maven-plugin's releases.

0.41.0 (2023-02-06):

• multi-arch build should use provided repository (1597) @​merikan
• new property docker.build.network to override the network for RUN directives for docker build (1636) @​tulinkry
• Update Jib Core to v0.23.0 (1637) @​rohanKanojia
• Update JNR UnixSocket to v0.38.19 (1638) @​rohanKanojia

Changelog

Sourced from docker-maven-plugin's changelog.

ChangeLog

• 0.42-SNAPSHOT :

• 0.41.0 (2023-02-06):

  • multi-arch build should use provided repository (1597) @​merikan
  • new property docker.build.network to override the network for RUN directives for docker build (1636) @​tulinkry
  • Update Jib Core to v0.23.0 (1637) @​rohanKanojia
  • Update JNR UnixSocket to v0.38.19 (1638)

• 0.40.3 (2022-12-18):

  • image/squash option is taken into account when using buildx (1605) @​kevinleturc
  • Allow having build args with same name but different value in various sources, which are overriden in the order of precedence in resulting build args map (1407) @​pavelsmolensky
  • Use double for docker.cpus property and interpret this value in the same way as Docker config option --cpus (1609) @​vjuranek
  • NPE from Assembly plugin when POM packaging is used (1146) @​slawekjaranowski
  • Docker pulling progress only shown after pull has completed and not in real-time (1598) @​causalnet
  • Bump org.yaml:snakeyaml to v1.32 (1619) @​pen4
  • Bump com.google.cloud.tools:jib-core to v0.23.0 (1620) @​pen4
  • Bump com.google.guava:guava to v31.1-jre @​rohanKanojia

• 0.40.2 (2022-07-31):

  • Plugin doesn't abort building an image in case Podman is used and Dockerfile can't be processed (1562) @​jh-cd
  • Bump gson from 2.8.5 to 2.8.9 (1556) @​dependabot
  • Build and load native platform during build goal, build and push all platforms during push goal (1576) @​chonton
  • Remove buildx cache, don't delete builder instances after goal. Use builder instance to cache artifacts (1579) @​chonton
  • Multiple assemblies use the name "maven". Please assign each assembly a unique name (1558) @​tbfky
  • Use https://index.docker.io/v1/ as default buildx server registry (1574) @​chonton
  • When using buildx, do not force build of native platform (1572) @​chonton

• 0.40.1 (2022-06-11):

  • buildx does not work when specifying Dockerfile location (1562) @​chonton
  • Use buildx, set tag to current version fails if it contains -SNAPSHOT (1566) @​chonton

• 0.40.0 (2022-05-29):

  • docker:stop should respect docker.skip even when docker.executeStopOnVMShutdown is set to true (1561) @​doyleyoung
  • Prevent concurrent access to secDispatcher during password decryption (1533) @​joserebelo
  • Support for docker run --sysctl parameters (1530) @​jpraet
  • Migrate to JUnit5 and Mockito for testing (1550) @​chonton
  • Multi-architecture images using buildx (1502) @​chonton
  • Add missing dash to buildx --build-arg (1559) @​elektro-wolle

• 0.39.1 (2022-02-27):

  • determineFinalArgValue respect default value if key exists but value is null (1528) @​twendelmuth

• 0.39.0 (2022-02-06):

  • skipPom is ignored by "push" goal (1482) @​rohanKanojia
  • Cleanup dangling images as a result of image tagging, auto-pulling a base image, or auto-pulling a cacheFrom image (#1513) @​rkhmelichek
  • Fix logic bug to remove dangling images in BuildService (1522) @​rkhmelichek
  • Enable Create Image (pull) HTTP API option (#1516) @​rohanKanojia

• 0.38.1 (2021-12-18):

... (truncated)

Commits

• daa5fb1 [RELEASE] Update project version to v0.41.0
• 8f249d0 deps : Update Jnr UnixSocket to v0.38.19
• 2505bf9 deps : Update jib-core to v0.23.0
• e816499 Update changelog.md
• 6c22fb3 remove copypasted unrelated name
• 6ffc72c update documentation for the new property
• bf02085 append missing comma to fix compilation
• e1b2905 rename NETWORK to BUILD_NETWORK
• 7d28536 add BUILD_NETWORK as ConfigKey
• da207a8 add network to property handler builder
• 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 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]

Failing Jobs - Building 1f8157a

Status	Name	Step	Failures	Logs	Raw logs
✔️	JVM Tests - JDK 11
✖	JVM Tests - JDK 11 Windows	Build	Failures	Logs	Raw logs
✔️	JVM Tests - JDK 17
✔️	JVM Tests - JDK 18

Full information is available in the Build summary check run.

Failures

⚙️ JVM Tests - JDK 11 Windows #

- Failing: integration-tests/mongodb-rest-data-panache 

📦 integration-tests/mongodb-rest-data-panache

✖ io.quarkus.it.mongodb.rest.data.panache.MongoDbRestDataPanacheTest.shouldNotCreateOrDeleteAuthor - More details - Source on GitHub

java.lang.RuntimeException: 
java.lang.RuntimeException: io.quarkus.builder.BuildException: Build failure: Build failed due to errors
	[error]: Build step io.quarkus.mongodb.deployment.DevServicesMongoProcessor#startMongo threw an exception: java.lang.RuntimeException: java.lang.IllegalStateException: Previous attempts to find a Docker environment failed. Will not retry. Please see logs and check configuration

[gsmet]

@loicmathieu apparently, this MongoDB test tries to use MongoDB Dev Services and thus Docker, which fails. Should it be adjusted somehow? (I see a resource that uses flapdoodle)

Also, should MongoDbRestDataPanacheIT also be enabled on Windows if we get the above to work?

[loicmathieu]

@gsmet it's stange as I tested multiple times the Windows CI/CD and all pass. We can disable it on Windows, the more important is to have some test on Windows for MongoDB, there should not be anything specific to Windows on Rest Data MongoDB with Panache. I'll have a look but migrating to TestResource to use Flapdoodle may also be feasible.