Ok. So the most simple solution seems to set KARAF_BASE to a r/w directory and to copy the /etc directory (before making it read-only) inside.
With that scenario, Karaf only complains about the "instances" directory which cannot be created BUT everything seems to work as expected. Does the "instances" failure can make any trouble? JP [@@ OPEN @@] -----Message d'origine----- De : Jean-Baptiste Onofré [mailto:[email protected]] Envoyé : mardi 16 juin 2015 13:42 À : [email protected] Objet : Re: Karaf installation to a read-only directory It's in the way (I created the JIRA for instances location). It's already possible for lock. Regards JB On 06/16/2015 01:18 PM, maggu2810 wrote: > I am using karaf in a read only installation. > - data > - instances > - lock > This directories / file are created. > > It would be nice, if ALL runtime data could be written elsewhere (not > only data, also instances and lock). > > > > -- > View this message in context: > http://karaf.922171.n3.nabble.com/Karaf-installation-to-a-read-only-di > rectory-tp4040942p4040948.html Sent from the Karaf - User mailing list > archive at Nabble.com. > -- Jean-Baptiste Onofré [email protected] http://blog.nanthrax.net Talend - http://www.talend.com
