[OPENIG-4760] Cannot mount local instance directory in read only mode with IG docker image Created: 07/Jul/20 Updated: 19/Aug/20 Resolved: 08/Jul/20
|Affects Version/s:||7.0.0, 7.0.0-micsvc-1.0.3|
|Fix Version/s:||7.0.0, 7.0.0-micsvc-1.0.3|
|Reporter:||Violette Roche Montane||Assignee:||Violette Roche Montane|
|Resolution:||Not a defect||Votes:||0|
|Remaining Estimate:||Not Specified|
|Time Spent:||Not Specified|
|Original Estimate:||Not Specified|
|Sprint:||2020.09 - IG / Microservices|
This issue applies both in gcr.io/forgerock-io/ig/docker-build and in the (not merged yet) standalone docker image.
The tmp folder in .openig is growing at each startup of IG, as far as I can see when running some tests, growing full of temporary empty folder named such as groovy-script-cache-1964974339709789650/ but that be a another issue.
As a user, I should be able to share my local IG configuration, in read-only mode, to be sure that nothing is altered, between my docker images.
|Comment by Laurent Vaills [ 07/Jul/20 ]|
Do not mount it as ro (read-only), or you can specify the location of the tmp directory through a setting in the admin.json file.
BTW, prefer the new option --mount .
|Comment by Violette Roche Montane [ 08/Jul/20 ]|
I created this issue as the :ro option is commonly used in docker world and keep track on that.
|Comment by Jean-Charles Deville [ 19/Aug/20 ]|
Closing issue after Release 7.0.0