Github user ddewaele commented on the issue:
https://github.com/apache/nifi/pull/1372
Hi @jdye64 ,
We also started using Nifi in a docker container using one of the
unofficial images (https://github.com/mkobit/docker-nifi).
Being able to use an official and supported Nifi Docker image would be
great.
Are you planning on adding data volumes for the repositories and the config
? (to avoid losing state / config).
We typically map
- database_repository
- flowfile_repository
- content_repository
- provenance_repository
- conf
- external config (variable registry)
How are you planning to handle custom processors in docker images ? We're
currently using a [docker maven
plugin](https://github.com/spotify/docker-maven-plugin) in Jenkins to build our
custom nifi image (extending the mkobit one), and we add our custom processors
in the docker image during build time (as everything needs to be in
${NIFI_HOME}/lib).
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
