-
Notifications
You must be signed in to change notification settings - Fork 27
Latest release breaks under Alpine #29
Comments
Hey @moritzheiber, something in the dependency chain more than likely depends on cgo by default, so probably built dynamic by default... this is definitely an oversight and not done intentionally. For now, you might have to build it by yourself either static or say within Alpine itself (so it links against musl). But I will add this as an enhancement for next release! |
No worries, I don't need to rely on the latest release. I'll just stick with 0.4.0 for the time being. Thank you for taking this up. |
Hi peepz! I've landed here because I've been a very happy customer of this great terraform provider until I've upgraded to version 0.5.0 and that broke my pipelines (that run on alpine). I'm not experienced with golang, but I needed to fix my pipelines so I've built the binary for this project in a Anyone not wanting to just download a binary off the internet and execute that blindly (would be a smart person and) can build it as well with the following steps:
Hope this helps anyone that lands here looking for it. |
I was able to get it working by just installing the "libc6-compat" package in alpine. |
I've just found this too. The Hashicorp Docker images run under Alpine so it would be nice to fix this so it works by default. @viyh's |
This works around a bug in the acme provider where the latest release is broken in Alphine: vancluever/terraform-provider-acme#29
Hey all! This should now be fixed with the 0.6.0 release:
Enjoy! |
Is there a reason as to why the latest release (0.5.0) is dynamically linked instead of statically? It breaks Alpine compatibility:
I know this isn't necessarily a target platform, but it looks like unwanted side-effect to me .. ?
Alpine version used is 3.7.0 (stable).
The text was updated successfully, but these errors were encountered: