3 ms·
I guess it's a bit more specific than you meant it, but our standard Python image is ~20MB (alpine + python3, basically); that's still under half of minideb. D
by pebers 9y ago
I guess it's a bit more specific than you meant it, but our standard Python image is ~20MB (alpine + python3, basically); that's still under half of minideb.
Does look interesting for things that need glibc compatibility though. There are some packages to help with that in Alpine but they only go so far.
- raesene6 9y agoYep. I like alpine and use it for my images for preference, but some things like getting Ruby on Rails working with therubyracer can bascially hit a wall in alpine, so this could be pretty handy.
- SjuulJanssen 9y agoIn my experience python in alpine is is sometimes 2x slower. How does ruby perform under Alpine?
- ridruejo 9y agoThanks, this is where I got the data from: https://dzone.com/articles/minideb-a-minimalist-debian-based-docker-image https://dzone.com/articles/minideb-a-minimalist-debian-based...
- pebers 9y agoFrom looking at what I think is the Dockerfile for that image (https://github.com/docker-library/python/blob/b1512ead24c6b111506a8d4229134a29da240597/2.7/alpine3.6/Dockerfile https://github.com/docker-library/python/blob/b1512ead24c6b1...), that image is complex; it's downloading & building Python in it and adding & removing a dev toolchain, in a few different layers. I'm not surprised that I got something a lot smaller from just running `apk add python3.6`, although as a result they are not comparing apples to apples; their minideb example does pretty much exactly the equivalent (i.e. downloading the distro-provided package, not compiling it within their image).