It means that your docker image is not immutable and after starting the
Karaf instance, it will download the updated dependencies features at
startup right?
It's not the common design for docker image and I think it's better to
have a custom Karaf distribution and build a new docker image
> Francois Papon :
> Why not using Jib?
> https://github.com/GoogleContainerTools/jib/tree/master
Unless I'm very mistaken that doesn't do what I want to do.
Jib looks like it is for containering a Java application?
What I'm doing is something different:
1. I start out with a standard
Hi,
Why not using Jib?
https://github.com/GoogleContainerTools/jib/tree/master
regards,
François
On 08/01/2024 19:36, Steinar Bang wrote:
Jean-Baptiste Onofré :
Hi Steinar
Let me check about the image type.
Did you find out anything?
The docker-maven-plugin I've been using (the one
> Jean-Baptiste Onofré :
> Hi Steinar
> Let me check about the image type.
Did you find out anything?
The docker-maven-plugin I've been using (the one created by spotify),
was abandoned a couple of years back:
https://github.com/spotify/docker-maven-plugin
So I've been trying to to use a
Hi Jean,
Thank you!
Well, I do not have a test case.
But I think the issue is regarding SCR feature.
This is the feature.
mvn:org.osgi/org.osgi.util.function/1.2.0
mvn:org.osgi/org.osgi.util.promise/1.2.0
mvn:org.osgi/org.osgi.service.component/1.5.0
