Starting v0.3.4 release asset binaries don't work in Alpine container

[antonfisher]

Hi, working on our CI, I noticed this.

Release v0.3.0-4 works fine but starting from release v0.3.4 asset binaries on releases page doesn't work in an Alpine container. The same is true for 1.0.2.

It seems like assets have been built with different flags than Makefile has because if I build the image from sources (using Makefile) it works in Alpine.

There are two one-liners to demonstrate the issue (I used Dockerfile.mock from the repo).
v0.3.0-4 (works):

$ curl -L https://github.com/kubernetes-csi/csi-test/releases/download/v0.3.0-4/csi-sanity-v0.3.0-4.linux.amd64.tar.gz | tar -xvz && mv csi-sanity/csi-sanity bin/mock && docker build -f Dockerfile.mock -t csi-sanity-local --no-cache . && docker run --rm -it csi-sanity-local
... curl output ...
Sending build context to Docker daemon  11.83MB
Step 1/5 : FROM alpine
... docker output ...
Successfully tagged csi-sanity-local:latest
--- FAIL: TestSanity (0.00s)
	sanity_test.go:53: --csi.endpoint must be provided with an CSI endpoint <--- IT WORKS
FAIL

v0.3.4 (doesn't work):

$ curl -L https://github.com/kubernetes-csi/csi-test/releases/download/v0.3.4/csi-sanity-v0.3.4.linux.amd64.tar.gz | tar -xvz && mv csi-sanity/csi-sanity bin/mock && docker build -f Dockerfile.mock -t csi-sanity-local --no-cache . && docker run --rm -it csi-sanity-local
... curl output ...
Sending build context to Docker daemon  11.89MB
Step 1/5 : FROM alpine
... docker output ...
Successfully tagged csi-sanity-local:latest
standard_init_linux.go:190: exec user process caused "no such file or directory" <--- DOESN'T WORK

Solutions that helped me:

• build binaries using Makefile
• use ubuntu container
• manually link missed libraries in my container RUN mkdir /lib64 && ln -s /lib/libc.musl-x86_64.so.1 /lib64/ld-linux-x86-64.so.2

Not sure that asset binaries supposed to work in Alpine, or manual image build is a recommended way to go.

This issue is similar to #127.

Thank you.

[EDIT]

• removed quay.io/k8scsi/mock-driver mention, thought it is csi-sanity container.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[msau42]

We no longer include binaries as part of the release so programs will need to be built separately
/close

[k8s-ci-robot]

@msau42: Closing this issue.

In response to this:

We no longer include binaries as part of the release so programs will need to be built separately
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.