the 3.5 was just released. we also provide an alpine-minirootfs.tar.gz that could be used for creation of the image.

Having a 3.5 image ASAP would be great. Who is able and going to take care of this?

It seems #240 handles getting 3.5 support into this repo, but the image tag's are either not built, or not appearing on the Docker Hub as yet...

@CpuID This is why docker hub still not upgrade: image is updated via pull requests to the docker-library/official-images GitHub repo.

this one needs to be merged: docker-library/official-images#2489

(you can close this now!)

I still cannot see gliderlabs/alpine:3.5 in tags on docker hub: https://hub.docker.com/r/gliderlabs/alpine/tags/ - any news on that?

@miketheman just do alpine:3.5.

@jbergstroem Thanks for the tip - I indeed tried that already. The gliderlabs version (which my stack is based upon) contains some differences (noted in http://gliderlabs.viewdocs.io/docker-alpine/build/ "Differences") that we currently use.

@miketheman oh; I didn't know that. Apologies.

@justincormack Here's what I get:

$ docker run -it --rm gliderlabs/alpine:3.4 ash
/ # apk-install
fetch http://alpine.gliderlabs.com/alpine/v3.4/main/x86_64/APKINDEX.tar.gz
fetch http://alpine.gliderlabs.com/alpine/v3.4/community/x86_64/APKINDEX.tar.gz
OK: 5 MiB in 11 packages
$ docker run -it --rm alpine:3.5 ash
/ # apk-install
ash: apk-install: not found

apk-install is a wrapper script that only does apk add --update "$@" && rm -rf /var/cache/apk/*.

Since then apk got its own flag to do the same so you can now do: apk add --no-cache ...

@ncopa Thanks for the update! That's great that apk now has a flag for it. Is the gliderlabs/alpine image now deprecated, i.e. will not receive updates? What about the Fastly-enabled packages distribution?

Closing as 3.5 has been released for some time now.