Open jbergstroem opened 3 years ago
How to understand information about disk space on main page?
# docker pull jbergstroem/mariadb-alpine
Using default tag: latest
latest: Pulling from jbergstroem/mariadb-alpine
339de151aab4: Already exists
d8a76355c986: Pull complete
ab79a022c72e: Pull complete
ac016432e3c2: Pull complete
c89f7e3be039: Pull complete
Digest: sha256:1f9d2015d9d7f3cc0d4a51c55d8d156192ad219889b81846fcbe07ec5119157d
Status: Downloaded newer image for jbergstroem/mariadb-alpine:latest
docker.io/jbergstroem/mariadb-alpine:latest
# docker images | grep "mar"
jbergstroem/mariadb-alpine latest 9690d1beda91 47 hours ago 34.3MB
kklepper/mariadb33-v10.5.9 alpine 5d0e51f6d14b 2 days ago 186MB
kklepper/mariadb33-v10.4.18 alpine 3e790d4ea6a1 2 days ago 43.6MB
kklepper/mariadb-alpine-v10.5.8 alpine e67b64b046df 3 days ago 37.5MB
kklepper/mariadb33-v10.1.26 alpine 19905a582f5a 4 days ago 112MB
demyx/mariadb latest 8452370517e1 8 days ago 190MB
mariadb latest eff629089685 2 weeks ago 408MB
ghcr.io/linuxserver/mariadb latest d6543d932fbf 3 weeks ago 352MB
wodby/mariadb latest 45eb42ec6a5e 5 weeks ago 272MB
yobasystems/alpine-mariadb latest 6229b748ebe8 5 weeks ago 231MB
kklepper/mariadb33 alpine 44b402734855 10 months ago 112MB
How to understand information about disk space on main page?
Good question! Docker hub tags usually show compressed size while docker locally shows uncompressed. I know it is confusing; not much to do.
Thank you, that explains it.
As part of a PR lifecycle, add info about the resulting container file size. This will be especially useful as features or versions are bumped.
Not sure if to add as a comment (read: one comment per new commit sha) or for instance editing the PR body.