Closed garrickstapleszed closed 6 years ago
It looks like you're using an Alpine-based container (apk add ...
) -- does the software you're looking to build support Alpine? Have you got a very minimal Dockerfile
which can reproduce the issue (what you've posted appears to be Step 13 of 19, and it's a long one, so doesn't seem very minimal)?
For my own gb
projects, I use gb
installed on my host to manage the project and build outside of Docker, but once I go to build inside Docker, I use GOPATH=/project/path:/project/path/vendor
to simply use native go build
/go install
within Docker (since I don't need gb
's additional functionality within the container -- I just need my code compiled into a usable binary).
Thank you for the reply. I'm happy to say that just changing from alpine:3.8 to golang:alpine fixed my problem. I guess private_s3_httpd doesn't like alpine's tiny libc; it needs the full glibc.
Hi all, I'm trying to use the 'private_s3_httpd' project. It is already set up to use gb. I can build it fine locally on Linux or OSX, but I get linking errors in Docker. Any suggestions on how to make this work?