syncope-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Wyllys Ingersoll (JIRA)" <>
Subject [jira] [Commented] (SYNCOPE-1345) domain configuration files do not persist across docker reloads
Date Thu, 26 Jul 2018 13:41:00 GMT


Wyllys Ingersoll commented on SYNCOPE-1345:


I modified the core startup script as follows to automatically copy anything it finds in the
/domain directory into place at startup so it is recognized. 

I then modified the compose script to have a named volume that mounts on /domain for that
container.  It seems to work, not sure if its something to consider for the main codebase
or not.  If it is, I can submit it formally.


{{--- a/docker/core/src/main/resources/}}
{{+++ b/docker/core/src/main/resources/}}
{{@@ -25,6 +25,12 @@ cd domains}}
{{ rm}}
{{ ln -s$DBMS}}

{{+if [ -d /domains ]; then}}
{{+ cp -f /domains/*.xml .}}
{{+ cp -f /domains/*.properties .}}
{{+ chown tomcat8:tomcat8 *}}
{{ /etc/init.d/tomcat8 start}}

{{ xtail /var/log/apache-syncope/*.log /var/log/tomcat8/}}

> domain configuration files do not persist across docker reloads
> ---------------------------------------------------------------
>                 Key: SYNCOPE-1345
>                 URL:
>             Project: Syncope
>          Issue Type: Improvement
>          Components: docker
>    Affects Versions: 2.0.9, 2.1.0
>            Reporter: Wyllys Ingersoll
>            Priority: Minor
> When using docker images - if additional domains are configured, their configuration
files must be manually copied to the docker image area )/var/lib/tomcat8/webapps/syncope/WEB-INF/classes/domains/)
to be with the Master.* files that are processed when syncope-core starts up.
> If the docker image is upgraded or re-loaded (down + up) the configuration files for
the additional domains are lost and must be manually copied over again and then the core
must be restarted.
> It would be great if there was a way to retain the domain configurations in a volume
mount or some other more persistent storage mechanism so that they are not lost when updating
or re-initializing the image.

This message was sent by Atlassian JIRA

View raw message