[
https://issues.redhat.com/browse/WFWIP-311?page=com.atlassian.jira.plugin...
]
Ken Wills commented on WFWIP-311:
---------------------------------
The size difference is likely not relevant yet. This dev preview build wasn't squashed
as It was built on my laptop with 5 other images, and in order to push the images to the
internal registry in a realistic timeframe, I wanted to get as much reuse from layer
caching as I could.
When we do an OSBS build, OSBS will squash by default, and this will likely not be an
issue.
OpenShift XP image doubled its size to 2GB compared to 7.3.0.GA 1GB
-------------------------------------------------------------------
Key: WFWIP-311
URL:
https://issues.redhat.com/browse/WFWIP-311
Project: WildFly WIP
Issue Type: Bug
Components: OpenShift
Reporter: Martin Choma
Assignee: Jeff Mesnil
Priority: Major
Attachments: Screenshot from 2020-04-23 06-56-37.png
I have started to play with OpenShift XP image
{{docker-registry.upshift.redhat.com/kwills/eap-xp1-openjdk8-openshift-rhel7:EAP7-1484}}
and I have noticed it is nearly 2GB big. Used to be 0.92 GB for 7.3.0.GA or CD19.
Also strange is there is much more layers compared to several layers in previous
releases
From dive output it seems every bash command result in own layer. Dive is reporting 624MB
of waste space.
!Screenshot from 2020-04-23 06-56-37.png|thumbnail!
I am setting priority just to major because it is not official image yet. But if this
will be the case of official image as well, I will raise priority. In OCP 4 there is no
image/layer cache so image must be "downloaded" for each build from registry
into pod.
[1]
{code}
docker-registry.upshift.redhat.com/kwills/eap-xp1-openjdk8-openshift-rhel... 1.93
GB
registry-proxy.engineering.redhat.com/rh-osbs/jboss-eap-7-eap73-openjdk11... 920
MB
registry-proxy.engineering.redhat.com/rh-osbs/jboss-eap-7-tech-preview-ea...
921 MB
{code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)