is installing 1.0.2k-r0
but it should install
1.0.2m-r0
is there a reason why?
The alpine:3.4 image was updated ~24 days ago, while the openssl package was ~18 days ago. We rely heavily on Docker build cache so that the images aren't constantly being rebuilt for no reason. Unfortunately there is nothing between the base image and the line in the Dockerfile installing openssl that would tell it to discard the docker build cache.
We could probably do something like we do in the tomcat images and pin a specific version so that we can force a build cache bust, but with the two CVEs (CVE-2017-3736 and CVE-2017-3735) fixed in 1.0.2m being "very difficult" and "not believed likely" to exploit it does not seem worth the effort at this time. I think we can instead wait for the next Alpine image rebuild.
"i am satisfied with my care" ~ Big Hero 6
thanks

Most helpful comment
"i am satisfied with my care" ~ Big Hero 6
thanks