You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
has anybody researched why is this? I see majority of downstream images are still based on buildpack-deps:jessie I believe this larger size hinders adoption of buildpack-deps:stretch
$ docker image ls buildpack-depsREPOSITORY TAG IMAGE ID CREATED SIZEbuildpack-deps latest 223c9ecff8eb 4 weeks ago 826MBbuildpack-deps stretch 223c9ecff8eb 4 weeks ago 826MBbuildpack-deps stretch-scm 8b8559aff3a2 4 weeks ago 273MBbuildpack-deps stretch-curl 6b9f0849e499 4 weeks ago 131MBbuildpack-deps jessie a00998d35d0b 4 weeks ago 610MBbuildpack-deps jessie-scm 3f8223a87be8 4 weeks ago 291MBbuildpack-deps jessie-curl 6eff593c35dd 4 weeks ago 168MB
The text was updated successfully, but these errors were encountered:
Yeah, that's definitely worth looking into -- checking which packages get installed in each via deps might be a good place to start digging (before getting crazy with diffing rootfs contents directly).
Closing, since this isn't an issue with the image, and is more an issue with Debian's packaging / dependencies changing between stretch and jessie (as noted above). 👍
has anybody researched why is this? I see majority of downstream images are still based on
buildpack-deps:jessie
I believe this larger size hinders adoption ofbuildpack-deps:stretch
The text was updated successfully, but these errors were encountered: