Switch golang base image to Debian in order to address libc linking p… #41
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
…roblem
Alpine has subistituted GNU libc with musl in 2014
(see https://www.alpinelinux.org/posts/Alpine-Linux-has-switched-to-musl-libc.html)
So if one builds ssl-proxy on Alpine, the linux binary will contain a reference to
the musl library. Since this library is not present in major linux distributions
(like Debian), launching ssl-proxy results in a "No such file or directory" error.
For more details on this problem see e.g.
https://www.reddit.com/r/golang/comments/64lz0s/how_to_crosscompile_libc_variants_like_musl/
https://stackoverflow.com/questions/54524785/how-to-build-a-go-executable-that-doesnt-link-to-musl-libc
Therefore the golang base image is switched from the Alpine to the Debian variant,
using it's most recent image of the 1.13 version line.