[
https://issues.apache.org/jira/browse/NIFIREG-236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16800777#comment-16800777
]
Michal Klempa commented on NIFIREG-236:
---------------------------------------
Hi [~bryan_rosander]
we are using NiFi Registry inside Docker, but decided to release "unofficial"
image for Registry.
You may take a look and test it:
[https://hub.docker.com/r/michalklempa/nifi-registry]
I was testing provisioning configuration files as bind mount points in
docker-compose and the startup script did not overwrite them, I have documented
conditions of overwriting in readme:
[https://github.com/michalklempa/docker-nifi-registry/blob/master/README.md#providing-configuration-by-mounting-files]
Feel free to use according to license and if any questions email me:
[[email protected]|mailto:[email protected]] or raise an issue at
GitHub https://github.com/michalklempa/docker-nifi-registry/issues.
Hope this helps.
> External configuration of docker container
> ------------------------------------------
>
> Key: NIFIREG-236
> URL: https://issues.apache.org/jira/browse/NIFIREG-236
> Project: NiFi Registry
> Issue Type: New Feature
> Reporter: Bryan Rosander
> Priority: Major
>
> In some environments (e.g. Kubernetes, docker-compose, etc) it is convenient
> to supply configuration files externally.
> In these deployment scenarios having immutable, easy to reason about
> configuration is desirable.
> To this end, we should be able to tell the registry's start.sh not to apply
> any changes to config files.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
