You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nifi.apache.org by "Aldrin Piri (JIRA)" <ji...@apache.org> on 2018/06/23 18:45:00 UTC
[jira] [Assigned] (MINIFI-441) Update Dockerfile to '0.4.0' and
better align with practices set in NiFi
[ https://issues.apache.org/jira/browse/MINIFI-441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aldrin Piri reassigned MINIFI-441:
----------------------------------
Assignee: Aldrin Piri
> Update Dockerfile to '0.4.0' and better align with practices set in NiFi
> ------------------------------------------------------------------------
>
> Key: MINIFI-441
> URL: https://issues.apache.org/jira/browse/MINIFI-441
> Project: Apache NiFi MiNiFi
> Issue Type: Improvement
> Reporter: Joseph Percivall
> Assignee: Aldrin Piri
> Priority: Major
>
> The DockerHub Dockerfile[1] still lists 0.2.0 (even though dockerhub is up to 0.4.0[2]). Also, it doesn't appear to follow best practices like the NiFi Dockerfile[3] does, such as tailing the log file for exposing to the docker log.
> Lastly, there doesn't appear to be any documentation on the expected way to pass the bootstrap.conf and config.yml files. I'm assuming that this is done by creating a volume at the expected config location but this should be documented since, unlike NiFi, the instance is essentially useless if a config.yml isn't passed.
> [1] https://github.com/apache/nifi-minifi/blob/master/minifi-docker/dockerhub/Dockerfile
> [2] https://hub.docker.com/r/apache/nifi-minifi/tags/
> [3] https://github.com/apache/nifi/blob/master/nifi-docker/dockerhub/Dockerfile
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)