Do you mean you have a race condition ? Regards JB
> Le 20 juin 2021 à 18:11, Jean-Baptiste Onofre <j...@nanthrax.net> a écrit : > > Just tested with Karaf 4.3.2: > > $ export > ORG_APACHE_KARAF_FEATURES_FEATURESREPOSITORIES="foo,mvn:no.priv.bang.sonar.sonar-collector/sonar-collector-webhook/LATEST/xml/features" > $ bin/karaf > karaf@root()> config:list "(service.pid=org.apache.karaf.features)" > ---------------------------------------------------------------- > Pid: org.apache.karaf.features > BundleLocation: ? > Properties: > featuresBoot = instance/4.3.2, package/4.3.2, log/4.3.2, ssh/4.3.2, > framework/4.3.2, system/4.3.2, eventadmin/4.3.2, feature/4.3.2, shell/4.3.2, > management/4.3.2, service/4.3.2, jaas/4.3.2, deployer/4.3.2, > diagnostic/4.3.2, wrap/2.6.7, bundle/4.3.2, config/4.3.2, kar/4.3.2 > featuresBootAsynchronous = false > featuresRepositories = > foo,mvn:no.priv.bang.sonar.sonar-collector/sonar-collector-webhook/LATEST/xml/features > felix.fileinstall.filename = > file:/Users/jbonofre/Downloads/apache-karaf-4.3.2/etc/org.apache.karaf.features.cfg > service.pid = org.apache.karaf.features > > So, you can see the featuresRepositories contains the env variable value. > > Regards > JB > >> Le 20 juin 2021 à 18:02, Steinar Bang <s...@dod.no> a écrit : >> >>>>>>> Steinar Bang <s...@dod.no>: >> >>> The apache/karaf:4.3.0 and apache/karaf:4.3.1 images both start fine in >>> docker on my dev machine. >> >>> I will try to build my image on top of 4.3.0 (I can't remember offhand >>> why I couldn't run on 4.3.1...?). >> >>> Possible complication here is that I have bumbed the karaf BoM to 4.3.2, >>> so I have built against something that is newer than the runtime...? >> >> This is with an image based on top of apache/karaf:4.3.0 >> >> From the output of "docker logs" >> https://gist.github.com/steinarb/d38767d99831e2816bc9d0a27d5a70ff >> it looks like the feature repository and boot features I tried to add in >> the Dockerfile weren't added: >> https://gist.github.com/steinarb/65225c3a491c0b08a4386778f4c84100 >> >> Are my environment variables and their content incorrect? >> >
