You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Opher Shachar (Jira)" <ji...@apache.org> on 2021/11/05 16:35:00 UTC

[jira] [Commented] (NIFI-5799) Unable to extend docker image with custom configuration

    [ https://issues.apache.org/jira/browse/NIFI-5799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17439369#comment-17439369 ] 

Opher Shachar commented on NIFI-5799:
-------------------------------------

Hello [~bhaard], unless I misunderstood you, you can execute your {{docker run}} command exactly as you typed it with the 1.14.0 Docker image available on DockerHub.

> 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.3.4#803005)