[
https://issues.apache.org/jira/browse/NIFI-7720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Murtaza Haji updated NIFI-7720:
-------------------------------
Description:
Right now the docker image doesnt designate `conf` folder to be committed to
new image. This causes the changes made in nifi(like building templates,
services etc.) to not be carried forward in new image. Can we make a change to
DockerFile to make sure this folder, that contains the flow.xml.gz file is
committed when creating new image.
For Reference:
[https://stackoverflow.com/questions/57520236/apache-nifi-docker-how-to-commit-changes-to-new-container]
was:
Right now the docker image doesnt designate `conf` folder to be committed to
new image. This causes the changes made in nifi(like building templates,
services etc.) to not be carried forward in new image. Can we make a change to
DockerFile to make sure this folder, that contains the flow.xml.gz file is
committed to docker when creating new image.
For Reference:
[https://stackoverflow.com/questions/57520236/apache-nifi-docker-how-to-commit-changes-to-new-container]
> Option to commit the flow.xml.gz file when generating new image from running
> container
> --------------------------------------------------------------------------------------
>
> Key: NIFI-7720
> URL: https://issues.apache.org/jira/browse/NIFI-7720
> Project: Apache NiFi
> Issue Type: Wish
> Components: Docker
> Reporter: Murtaza Haji
> Priority: Minor
> Labels: newbie
>
> Right now the docker image doesnt designate `conf` folder to be committed to
> new image. This causes the changes made in nifi(like building templates,
> services etc.) to not be carried forward in new image. Can we make a change
> to DockerFile to make sure this folder, that contains the flow.xml.gz file is
> committed when creating new image.
>
> For Reference:
> [https://stackoverflow.com/questions/57520236/apache-nifi-docker-how-to-commit-changes-to-new-container]
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
