[
https://issues.apache.org/jira/browse/NIFI-5799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre Villard resolved NIFI-5799.
----------------------------------
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.
> Unable to extend docker image with custom configuration
> -------------------------------------------------------
>
> Key: NIFI-5799
> URL: https://issues.apache.org/jira/browse/NIFI-5799
> Project: Apache NiFi
> Issue Type: Bug
> Components: Docker
> Affects Versions: 1.8.0
> Reporter: Noel Winstanley
> Priority: Major
>
> I build a custom docker image for my product, based on the stock docker nifi
> image.
> My Dockerfile installs a flow.xml.gz, and then uses sed to adjust some
> properties in conf/bootstrap.conf and conf/nifi.properties. This worked well
> with previous versions of Nifi
> https://issues.apache.org/jira/browse/NIFI-5438 (introduced in Nifi 1.8.0)
> added a VOLUME command to the docker file that covers ${NIFI_HOME}/conf .
> I am still able to copy a new flow.xml.gz into the conf directory, BUT am
> unable to edit files already in the conf dir (using sed or otherwise).
> This surprising behaviour is backed up by the dockerfile docs
> https://docs.docker.com/engine/reference/builder/#volume - "
> *Changing the volume from within the Dockerfile*: If any build steps change
> the data within the volume after it has been declared, those changes will be
> discarded. "
> The properties I wish to override (e.g. nifi.bored.yield.duration) aren't
> supported as environment variables, so I can't pass them in from a compose
> file or similar.
> Having a VOLUME command over a configuration directory really hampers the
> extensibility of the docker image - could it be removed?
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
