[
https://issues.apache.org/jira/browse/NIFI-3260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15798413#comment-15798413
]
ASF GitHub Bot commented on NIFI-3260:
--------------------------------------
Github user jdye64 commented on the issue:
https://github.com/apache/nifi/pull/1372
Good point about Docker ARG. If the plugin doesn't currently support I'm
sure it would be an easy add.
Sorry I wasn't very clear there. I was thinking about a more infrastructure
level. For us to actually host our official image on Dockerhub there must be a
unique tag, commit, and directory that points to our Dockerfile for a specific
Docker tag. So if we had a minor release we would need to create a new
directory. That is why in this commit I have the two directories "1.1.0" and
"1.1.1" to illustrate that. I don't like that structure at all but it almost
seems necessary to host via Dockerhub. This is somewhat of a limitation for
"official" images only which most likely other users of the docker-maven-plugin
are not doing but rather making internal release and sending to their own
private docker repos.
So when we made a PR to https://github.com/docker-library/official-images
our PR would be a single file looking something like ...
https://github.com/docker-library/official-images/blob/master/library/storm
> 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)
