Preconditions.checkArgumentmight be overkill, but at least the
@JsonCreatortakes care of the final field issue
hi. i'd like to push the image to aws-ecr and as such have configured a credsHelper as the jib docs suggest and am running into the following error, noting the what looks to be typo in the tool name:
...The system does not have docker-credential-erc-login CLI
i have brew installed docker-credential-ecr-login. thoughts?
Registry may not support pushing OCI Manifest or Docker Image Manifest Version 2, Schema 2The reason is we have tag immutability turned on in ECR.
jibDockerBuildtask to do a push? The setup I have now is
./gradlew jibDockerBuildand then a shell script that runs a
docker push builtIimageNamewhich pushes to ECR. it would be kinda nice to have a
jibDockerPushwhich would just run docker push on whatever the jibDockerBuild task built.
[ERROR] Failed to execute goal com.google.cloud.tools:jib-maven-plugin:1.6.1:dockerBuild (build-local-image) on project oai-identifiers-harvester: Build to Docker daemon failed, perhaps you should make sure Docker is installed and you have correct privileges to run it -> [Help 1]
Trouble overwriting a file from a base image.
I have the following snippet in my maven pom:
<extraDirectories> <paths> <from>src/main/docker/sysconfig</from> <into>/etc/sysconfig</into> </paths> </extraDirectories>
sysconfig exists in my base image. No files are copied. What do I miss?
Hello, is there a way to provide a command line argument in order to forgo a property defined?
For jib on my local machine, I use:
But for building/publishing in CI environment, I want to use specific credentials, while omitting property defined at
jib.to.credHelper. Is this possible?
*-docker.pkg.dev), Jib now tries Google Application Default Credentials last like it has been doing for
/app/jib-main-class-file. They hold, respectively, the final Java runtime classpath and the main class computed by Jib that are suitable for app execution on JVM. For example, with Java 9+, setting the container entrypoint to
java --class-path @/app/jib-classpath-file @/app/jib-main-class-filewill work to start the app. (This is basically the default entrypoint set by Jib when the entrypoint is not explicitly configured by the user.) The files are always generated whether Java 8 or 9+, or whether
jib.container.entrypointis explicitly configured. The files can be helpful especially when setting a custom entrypoint for a shell script that needs to get the classpath and the main class computed by Jib, or for GoogleContainerTools/jib#2471. (GoogleContainerTools/jib#3280)
java -cp @/app/jib-classpath-file). As such,
jib.container.expandClasspathDependenciestakes no effect for Java 9+. (GoogleContainerTools/jib#3280)
jibBuildTarare set to the epoch, making the tarball reproducible. (GoogleContainerTools/jib#3158)
jib.container.labelsusing Gradle Property and Provider. (GoogleContainerTools/jib#3242)
jib.container.entrypointis configured. (GoogleContainerTools/jib#3295)
@/all Jib Core 0.19.0 has been released!
Major Changes for Jib Core
JavaContainerBuilder#fromDistrolessJetty()are deprecated. To migrate, check the Javadoc. (GoogleContainerTools/jib#3123)
TarImageare set to the epoch, making the tarball reproducible. (GoogleContainerTools/jib#3158)
See CHANGELOG.md (Jib Core) for more details.
@/all Jib CLI 0.7.0 has been released!
warcommand which can be used to containerize a standard WAR with
$ jib war --target ... my-app.war. The command will explode out the contents of the WAR into optimized layers on the container. (GoogleContainerTools/jib#3285)
See CHANGELOG.md for more details.
It's a multi-module project, the build seems to complete, but when getting to:
[1m[====== ] 20.0% complete[0m [1m> building dependencies layer[0m [1m> building project dependencies layer[0m [1m> building classes layer[0m [1m> building resources layer[0m [1m[0m
@/all Jib Build Plugins 3.1.2 released with the following bug fix:
jib.applicationCacheto some shared dir in Maven? I understand that for Gradle with its incremental build jib can be informed by Gradle that there is no need to build the application layer, so instead it use the cached one. But for what I understand, there is no such feature in Maven, so setting jib.applicationCache does not help with anything, right?