Tiller-proxy depends on Alpine image

[prydonius]

The production docker image for the tiller-proxy depends on Alpine (https://github.com/kubeapps/kubeapps/blob/master/cmd/tiller-proxy/Dockerfile#L1). Is there any particular reason for this (apart from debugging, for which we can always use a different image), and if not can we modify the Dockerfile to use scratch like the other Go services (using alpine in multi-build to copy over SSL certs)?

[andresmgot]

when installing the package ca-certificates it installs files in several places which could be a bit tricky to modify. I am okay doing that but what's the benefit of using scratch vs other image?

[prydonius]

Go looks for certs in /etc/ssl/certs so it should be sufficient to copy the bundle into there like we do in the other Dockerfiles: https://github.com/kubeapps/kubeapps/blob/master/cmd/chart-repo/Dockerfile#L8.

what's the benefit of using scratch vs other image?

smaller image and not having to keep a base image version up-to-date, also we're using scratch in all the other Go-based images