[
https://issues.apache.org/jira/browse/NIFI-3260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15798376#comment-15798376
]
ASF GitHub Bot commented on NIFI-3260:
--------------------------------------
Github user achristianson commented on the issue:
https://github.com/apache/nifi/pull/1372
@jdye64 If we do end up going the route of injecting the build #,
Dockerfile ARG statements might be the way to go. The docker-maven-plugin would
be the place to set the arg, if that plugin supports it. Unsure if they do.
What sort of image maintenance are you concerned with? Are you talking
about going back and releasing minor releases? In my experience with docker,
the way it would work is with image tags. E.g. the "centos7" tag of the
official "centos" image tracks the 7.x release. This would be analogous to a
"nifi1.0.x" or "nifi-1.1.x" tag, or however it would best be named. In that
arrangement, it would come down to compatibility between versions. If I'm
running a production release of nifi 1.1.x, I want to get the latest
bugfixes/patches, but I do not want to be upgraded to an incompatible version,
i.e. 1.2.x.
> 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)
