[
https://issues.apache.org/jira/browse/NIFI-3260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15786183#comment-15786183
]
ASF GitHub Bot commented on NIFI-3260:
--------------------------------------
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).
> Official Docker Image
> ---------------------
>
> Key: NIFI-3260
> URL: https://issues.apache.org/jira/browse/NIFI-3260
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Tools and Build
> Reporter: Jeremy Dyer
> Assignee: Jeremy Dyer
>
> This JIRA is for setting up a Docker folder structure within the NiFi source
> code as discussed in the dev mailing list at
> https://lists.apache.org/thread.html/e905a559cb01b30f1a7032cec5c9605685f27a65bdf7fee41b735089@%3Cdev.nifi.apache.org%3E
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)