[
https://issues.apache.org/jira/browse/NIFI-4057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16091781#comment-16091781
]
ASF GitHub Bot commented on NIFI-4057:
--------------------------------------
Github user apiri commented on the issue:
https://github.com/apache/nifi/pull/1910
Those images are created automatically from release tags (e.g.
rel/nifi-1.2.0) on the source code repository. Those tags are protected and
immutable on the repository; once they are created they cannot be overwritten
whatsoever. It is this standard that prevents us from replacing the images.
As a project community, we have no permissions to directly interact with Apache
Docker Hub account which is managed by the Infra team.
As mentioned, if a patch version of either those comes out, we can port
these changes to that release branch as well. If we were to break docker
components out into their own repo, we could overwrite those tags on Docker
Hub. Unfortunately, until the source repo of the Dockerfile changes, those
versions in Docker Hub are locked to the associated commits that generated them.
> Docker Image is twice as large as necessary
> -------------------------------------------
>
> Key: NIFI-4057
> URL: https://issues.apache.org/jira/browse/NIFI-4057
> Project: Apache NiFi
> Issue Type: Bug
> Components: Docker
> Affects Versions: 1.2.0, 1.3.0
> Reporter: Jordan Moore
> Assignee: Jordan Moore
> Priority: Minor
> Fix For: 1.4.0
>
>
> By calling {{chown}} as a secondary {{RUN}} command, you effectively double
> the size of image by creating a Docker layer of the same size as the
> extracted binary.
> See GitHub discussion:
> https://github.com/apache/nifi/pull/1372#issuecomment-307592287
> *Expectation*
> The resultant Docker image should be no larger than the Base image + the size
> required by extracting the Nifi binaries.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
