@ZealousMacwan -- Hey, try these instructions for building an image to a local docker daemon with Jib: https://github.com/GoogleContainerTools/jib/blob/master/docs/faq.md#can-i-build-to-a-local-docker-daemon
I think this is what you want.
I had a multi-stage dockerFile where I'm setting up graalvm environment, copying the jars from my project and then building a native image in the first layers, and then copying the resulting artifacts to the last layer.
Would this kind of building scenario be possible using Jib?
I have been using jib on various projects for more than a couple years. Had a problem recently with AWS Fargate where running local version of container on a mac would work fine and running on AWS errored out due to duplicate methods. Somehow the classes load order changed from local container to AWS. Same application had similar issue with just a restart on Fargate where again classes load order failed the application launch (missing method on the core version of a transitive lib version).
I understand that I can look for duplicate methods and fix this at build time but Spring Boot already has mechanism to enforce class load order through JarLauncher. Is there a mechanism in jib to enforce class load order?
I was trying to containerize a legacy project where its JAR contains multiple entry points (classes with main() method). All those different classes are called by a scheduler and using a *.sh script.
But Jib gave me an error because of the multiple valid main classes.
Is there any way to work around this need to have a single entry point?
doppler run -- <command>. What I would like to do is just prefix the default entrypoint with
["doppler", "run", "--"]without completely overwriting the default one. Any help would be appreciated.
extraDirectoriesin the jib gradle plugin
A problem occurred evaluating project ':tourlandish.aries'. > Cannot set the value of read-only property 'from' for extension 'jib' of type com.google.cloud.tools.jib.gradle.JibExtension.
I am trying to understand the base image cache directory structured specified by
-Djib.baseImageCache and how it works.
bash-5.0$ tree /tmp/baseimage10/ /tmp/baseimage10/ -- images -- myregistry.jib.com -- myrepo -- myimage!sha256!mysha |-- lock -- manifests_configs.json
Where are the actual layers stored?
Hi @/all, I'm struggling to understand, is there any guides on how i can use Jib and cloud build together? thanks
hi guys, is there any updated preferred way to use jib with gradle on google cloud build? is it possible to use gradlew instead of preinstalled gradle image?
Hi jib team, thanks for the plugin for Maven, like it; I am using the buildTar task, and find this error message:
Caused by: java.nio.file.NoSuchFileException: /tmp/2158944339627963675/manifest.json ... at com.google.cloud.tools.jib.builder.steps.LocalBaseImageSteps.cacheDockerImageTar (LocalBaseImageSteps.java:217) ...
When I want to read a tarball in
The image I downloaded is
registry.access.redhat.com/jboss-amq-6/amq63-openshift:1.4-44. I want to
docker save it to a tar, extract it, enter each layer and remove some class file, and package it again as a tarball, and build my app with
buildTar. But I failed with this error. (Yes, I do this because I need to remove some log4j class files).
Do you think it's the proper way? What did I do wrong? Thanks. Plugin version 3.0.0, command:
mvn clean package jib:buildTar -U -f pom.xml -P docker-build -X. Maven is using Java 8.