Help Center/ Software Repository for Container/ FAQs/ Other FAQs/ Why Is an Image Pushed Using a Container Engine Client to SWR Different in Size From One Uploaded Through the SWR Console?
Updated on 2024-10-21 GMT+08:00

Why Is an Image Pushed Using a Container Engine Client to SWR Different in Size From One Uploaded Through the SWR Console?

Symptom

Assume that a nginx image of v5 is created on the local Docker client. The docker images command is run to query SIZE of the image. The size is 22.8 MB.

$ docker images
REPOSITORY                         TAG             IMAGE ID       CREATED         SIZE
nginx                              v5          22f2bf2e2b4f   9 days ago      22.8MB
  1. Run the docker push command to push the image to SWR. The size of the image is 9.5 MB.

  2. On the local Docker client, pack the image into a TAR package. Download the nginx.tar package to the local host, and upload the package to SWR. The size of the package is 23.2 MB.

The size of the image pushed through the client is different from that of the image uploaded through the SWR console.

Possible Cause

Image layers are compressed into TGZ packages when images are pushed to SWR using a container engine client, whereas when they are uploaded through the SWR console, they are only packed without being compressed. Therefore, the same image will be of different sizes when it is uploaded in these two different ways.