[
https://issues.apache.org/jira/browse/NIFI-10360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre Villard resolved NIFI-10360.
-----------------------------------
Resolution: Feedback Received
Apache NiFi 1.x is no longer maintained and no new release is planned on the
1.x release line. Marking as resolved as part of a cleanup operation. Please
open a new one with an updated description if this is still relevant for NiFi
2.x.
> VOLUME declaration prevents updating flow from CI
> -------------------------------------------------
>
> Key: NIFI-10360
> URL: https://issues.apache.org/jira/browse/NIFI-10360
> Project: Apache NiFi
> Issue Type: Bug
> Components: Docker
> Affects Versions: 1.16.0, 1.17.0
> Reporter: Vitalii Zhakov
> Priority: Major
> Time Spent: 2.5h
> Remaining Estimate: 0h
>
> Hello!
> I have CD pipeline:
> 1) build docker image with Nifi flow
> FROM apache/nifi:1.16.0
> USER nifi
> COPY --chown=nifi ./build_env/images/nifi/drivers/ /opt/nifi/nifi-current/lib/
> COPY --chown=nifi ./build_env/images/nifi/project/conf/
> /opt/nifi/nifi-current/conf/
> CMD ["../scripts/start.sh"]
> 2) deploy to registry
> 3) run docker container FROM registry's image
> VOLUME declaration prevents getting changes from image (container used data
> in /opt/nifi/nifi-current/conf/ from local volume instead of registry).
> Deleting container and starting new get changes to Nifi's flow, but system
> has 7 garbage volumes every deploy.
> Maybe creating VOLUME in Dockerfile is atavism now?
> If user removes contaner, docker creates new VOLUME and data will be lost.
> VOLUME instructions created in NIFI-5438
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
