[
https://issues.apache.org/jira/browse/SOLR-15891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17472164#comment-17472164
]
ASF subversion and git services commented on SOLR-15891:
--------------------------------------------------------
Commit 5690007225067a8106a2d14415d03eb1c141dba1 in solr's branch
refs/heads/main from Houston Putman
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=5690007 ]
SOLR-15891: Shrink Solr image, use default tarball file permissions (#498)
> The Solr docker image is roughly 1.5-2x the size it needs to be
> ---------------------------------------------------------------
>
> Key: SOLR-15891
> URL: https://issues.apache.org/jira/browse/SOLR-15891
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: Docker
> Affects Versions: 9.0
> Reporter: Houston Putman
> Priority: Blocker
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Currently the local (and test-official) docker images built off of 9x (main)
> are 1.5-2x the size of the docker images created for 8.x releases.
> You can see this in the [official nightly builds docker
> image|https://hub.docker.com/r/apache/solr-nightly/tags], when you click on
> the image tag.
> The reason for this is we change the permission of each Solr file/directory
> that we have either 1) just downloaded (in the official docker image) or 2)
> just copied (in the local docker image), in this line:
> [https://github.com/apache/solr/blob/main/solr/docker/templates/Dockerfile.body.template#L34]
> One easy fix is to do this step in the same download step in the official
> docker file, so that no additional space is used up for that layer. However,
> since the copy task does not allow for changing permissions at the same time,
> local docker builds will continue to have the same size issues.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
