gradle-docker | Gradle plugin to build Docker images | Continuous Deployment library

Got answer from below url and this will fixed my issue

https://discuss.gradle.org/t/annotation-processor-org-hibernate-jpamodelgen-jpametamodelentityprocessor-not-found/30823

I think this is equivalent, though I think it just knocks Java out of the picture, so Groovy/Kotlin/Java buildSrc code won't work...:

Have a look at the Javadoc for versions 2.1.11 and 2.2.4 respectively. The older version still exposes this method taking an int argument but already states that it's deprecated and that you should use java.time.Duration instead.

The method accepting java.time.Duration still exists in 2.2.4 and you should use that one instead.

It may be related to your java version.

Gradle added support for TLSv3 on the 14.11.2019 (and disabled TLSv1.0) in plugins.gradle.org, and it seems that "old" Java versions have problems with it:

https://status.gradle.com/incidents/q2vq49fndxg0

For us it failed with 11.0.1, and we had to upgrade to 11.0.5

One way to achieve your goal is to create ${PWD}/config/grade-docker.properties file on the host where ${PWD}/docker-compose.yml... ${PWD} for clarity.

Your existing volumes property will then map this file into the container when it's run and place it in the container's /config.

The app.jar should be an executable jar file but it is instead a directory. Because the JAR_FILE is not set as build argument the COPY instruction copies the content of the /build/docker directory to the /app.jar directory in the container. You can list it with:

I have a working project with spring cloud stream and zipkin using the following configuration (maybe you should set the sender.type):

My gradle.properties file was missing with the username, PW, and URL. Replacing it with that information allowed me to import projects again and perform non-bootRun Gradle tasks.

It got deleted at some point before I reinstalled Gradle and I never replaced it due to panic that my Gradle wasn't working any longer.

Well, it's still not properly working, but I can import projects again, so I can at least get by with IntelliJ's compiler.

The stuff you add in the closure for the task is applied when Gradle is configuring your tasks - not when actually running them. So in this case, you are defining two tasks, and both of them sets a shared property project.group. So whatever task happens to be configured last "wins", no matter which one you actually intend to run.

There are many Docker plugins for Gradle available, and it looks to me like you use the one from Transmode. From the documentation, it appears you can't build two images with different Docker repository names in the same Gradle project. So I would say your options are to either set the name yourself after the image is built (e.g. in a doLast block), split it into two Gradle projects, or use another Docker plugin that is more customizable. The one from bmuschko is probably the most widely used and feature rich.