Compression of Mashery Local images
Article ID: KB0074557
Updated On:
| Products | Versions |
|---|---|
| TIBCO Cloud API Management - Local Edition | 5.x |
Description
After building images in Jenkins, we see the following sizes (size may vary a bit in different environments) of Mashery Local v 5.3.1 images.
When we "push" these images to a container registry, the sizes change to:
tml-cache 323.57MB
tml-cm 486.41 MB
tml-log 371.36 MB
tml-nosql 316.29 MB
tml-sql 595.95 MB
tml-tm 384.64 MB
tml-cache 713MB
tml-cm 1.03GB
tml-log 922MB
tml-nosql 658MB:
tml-sql 1.56GB
tml-tm 787MB
When we "push" these images to a container registry, the sizes change to:
tml-cache 323.57MB
tml-cm 486.41 MB
tml-log 371.36 MB
tml-nosql 316.29 MB
tml-sql 595.95 MB
tml-tm 384.64 MB
Issue/Introduction
Compression of Mashery Local images
Environment
N/A
Resolution
When we (docker) push images to container registry, the images are compressed during the push. This is the reason for size difference of images.
Feedback
Yes
No
Powered by
