Re: Is the karaf 4.4.4 docker image arm only?
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 after each dependencies update. But it's just my opinion for the Karaf docker image usage :) regards, François On 08/01/2024 20:45, Steinar Bang wrote: 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 karaf image 2. Then I create a Dockerfile that replaces the org.apache.karaf.features.cfg file with a file that a. has the applications feature repository added to featuresRepositories b, adds the application's feature to featuresBoot So I provision the application using maven and use LATEST, which means I don't have to update the image when the application is updated, I just restart the docker image and it pulls the latest version of the app from maven. That is: I will have to update the image when the world has changed too much (what fails right now is that OSGi 6 can't run OSGi 8 applications, and I can see that the Java version I'm building with can be an issue). I'm trying to create a new docker image for sonar-collector right now, but that is the first time in two years (I don't use the docker image myself, but apparently someone else did and ran into trouble recently).
Re: Is the karaf 4.4.4 docker image arm only?
> 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 karaf image 2. Then I create a Dockerfile that replaces the org.apache.karaf.features.cfg file with a file that a. has the applications feature repository added to featuresRepositories b, adds the application's feature to featuresBoot So I provision the application using maven and use LATEST, which means I don't have to update the image when the application is updated, I just restart the docker image and it pulls the latest version of the app from maven. That is: I will have to update the image when the world has changed too much (what fails right now is that OSGi 6 can't run OSGi 8 applications, and I can see that the Java version I'm building with can be an issue). I'm trying to create a new docker image for sonar-collector right now, but that is the first time in two years (I don't use the docker image myself, but apparently someone else did and ran into trouble recently).
Re: Is the karaf 4.4.4 docker image arm only?
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 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 docker-maven-plugin that is maintained: https://github.com/fabric8io/docker-maven-plugin I've succeeded in building a sonar-collector docker image using the new docker-maven-plugin, but I end up with an arm64 image here as well (even though I'm building and running on amd64): https://github.com/fabric8io/docker-maven-plugin/issues/1739#issuecomment-1881260436
Re: Is the karaf 4.4.4 docker image arm only?
> 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 docker-maven-plugin that is maintained: https://github.com/fabric8io/docker-maven-plugin I've succeeded in building a sonar-collector docker image using the new docker-maven-plugin, but I end up with an arm64 image here as well (even though I'm building and running on amd64): https://github.com/fabric8io/docker-maven-plugin/issues/1739#issuecomment-1881260436
Re: Karaf version with Jdk 21
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 mvn:org.apache.felix/org.apache.felix.metatype/1.2.4 mvn:org.apache.felix/org.apache.felix.scr/2.2.6 management mvn:org.apache.karaf.scr/org.apache.karaf.scr.management/4.4.4 webconsole mvn:org.apache.felix/org.apache.felix.inventory/1.1.0 mvn:org.apache.felix/org.apache.felix.webconsole.plugins.ds/2.2.0 bundle mvn:org.apache.karaf.scr/org.apache.karaf.scr.state/4.4.4 osgi.service;effective:=active;objectClass=org.apache.felix.scr.ScrService, osgi.extender;osgi.extender="osgi.component";uses:="org.osgi.service.component";version:Version="1.2.1" And this is the error I'm facing while running karaf. org.apache.felix.resolver.reason.ReasonException: Unable to resolve root: missing requirement [root] osgi.identity; osgi.identity=7db4b9c9-5d8b-4144-a2b3-2162c2867296; type=karaf.feature; version="[0,0.0.0]"; filter:="(&(osgi.identity=7db4b9c9-5d8b-4144-a2b3-2162c2867296)(type=karaf.feature)(version>=0.0.0)(version<=0.0.0))" Caused by: org.apache.felix.resolver.reason.ReasonException: Unable to resolve cloudforwarder-log-config/1.6.0.0003: missing requirement ["modulename"] osgi.extender; filter:="(&(osgi.extender=osgi.component)(version>=1.4.0)(!(version>=2.0.0)))" Regards, From: Jean-Baptiste Onofré Sent: Saturday, January 6, 2024 9:46 AM To: user@karaf.apache.org Subject: Re: Karaf version with Jdk 21 CAUTION: This email originated from outside our organization. Do not click links or open attachments unless you validate the sender. Hi 4.4.5 will be in vote today with better support of JDK21 (we build and test using JDK20, I will setup JDK21). Regarding 4.5.0 (including Jakarta EE namespace), I plan to work on it in the coming days. I hope to submit 4.5.0 to vote in a couple of weeks. Do you have specific test cases with JDK21 ? I would like to check with Karaf 4.4.5. Regards JB On Fri, Jan 5, 2024 at 9:12 PM yunji@toshibagcs.com wrote: > > Hi Jean, > > Thank you for providing the information. > > I'm currently in the process of migrating from Karaf 4.2 to 4.4 due to our > migration from Java 8 to Java 21. > However, I've encountered some errors while running Karaf, seemingly related > to the OSGi component (likely associated with the SCR feature). > Could you please provide information on the scheduled release date for Karaf > 4.5? > > Thanks again for your assistance. > > Best regards, > > Yunji Lee > > > > > From: Jean-Baptiste Onofré > Sent: Wednesday, December 13, 2023 8:36 AM > To: user@karaf.apache.org > Subject: Re: Karaf version with Jdk 21 > > CAUTION: This email originated from outside our organization. Do not click > links or open attachments unless you validate the sender. > > > > Hi Yunji > > I'm preparing 4.4.5 right now, but a better JDK 21 support (but not > yet complete due to third parties like Aries *). > > About Karaf 4.5.0, I plan to submit it to release just after Christmas. > > Regards > JB > > On Mon, Dec 11, 2023 at 5:03 PM yunji@toshibagcs.com > wrote: > > > > Hello good day, > > > > I hope this email finds you well. > > I was trying to compile and run karaf 4.4.4 on jdk21. > > > > And I came across information in the mailing list that there will be a > > Karaf 4.5.x version with full JDK 21 support. > > I'm interested to know when this release is scheduled. > > > > Thank you for your time and assistance. > > > > Best regards, > > Yunji Lee
