search

linuxep / lepv

web backend and frontend for LEP
20 stars 31 forks source link

Why pushing such a big amount of data to Docker Hub #28

Open linuxep opened 7 years ago

linuxep commented 7 years ago

LEPV docker image is based on Linux/Python3, when I tried to push LEPV image( with pushDockerImage.sh ), it pushes a lot of Layers, which is HUGE in size.

I don't need all those layers, I just want to push just the delta/changes from the original image, so users will see a much shorter time downloading the image:

the push refers to a repository [docker.io/linuxep/lepv] 2f4463269f88: Pushing [=======> ] 2.312 MB/15.2 MB 19633397d381: Pushed 3f43d97eee03: Pushing [===> ] 1.438 MB/20.1 MB db42a5e91d18: Layer already exists b9cb5d9bab14: Layer already exists 8ce66f40b4c3: Layer already exists 2b2d42632b0e: Layer already exists 5d8b38261598: Layer already exists 86f94a29e6a2: Layer already exists fa6e25b2e1bd: Waiting 53ad72233c22: Waiting 2ab3bce6e3ea: Layer already exists e40191ba235d: Waiting 2101d3c01933: Waiting 751f5d9ad6db: Waiting 17587239b3df: Waiting 9e63c5bce458: Waiting

linuxep commented 7 years ago

maybe... I should upload another "LEPV Base" image first, and "FROM" that image for each LEPV image so only the "lepv" code change is included in the "delta", not the "static" environment settings .

will try more.

and expecting Joy Zhou to input here.

chowyu08 commented 7 years ago

@linuxep 1, If we mount all the django file when run the container, the image maybe smaller, but the python image is must. 2, If we use docker compose , the image is useless, need not push to dockerHub. 3, In Mainland, access dockerhub is slow, you should add a mirror source like Alibaba or DaoCloud.