splicectl doesn't work under alpine image

[voron]

SSIA

How to reproduce:

docker run -it --rm --name alpine0 alpine
apk add wget file
wget https://github.com/splicemachine/splicectl/releases/download/v0.1.2/splicectl_linux_amd64.tar.gz
tar xzf splicectl_linux_amd64.tar.gz
cd splicectl_linux_amd64/
./splicectl 

And the output is

/bin/sh: ./splicectl: not found

The issue is that splicectl binary is dynamically linked

 file ./splicectl 
./splicectl: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, Go BuildID=tsMujqG3KViSUK7B3nLx/a8C3_FLS46xKOUGkagqH/Y33HjfeHBC602P2U0DzD/rlmmoTDLyw0CS-ZJOQd9, not stripped

Temporary work-around is to install libc6-compat

 apk add libc6-compat

I suppose the correct way should use is to build static binaries.

We have kubectl as an example - it works w/o issues in the vanilla alpine image as it's static binary

file ./kubectl
./kubectl: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), statically linked, stripped

[RileyMcCuen]

This can be solved by either symlinking to the muslc lib in the dockerfile (the c lib that Alpine uses instead of glibc) or by compiling the go binaries with CGO_ENABLED=0, which will force go to include go implementations of the networking library instead of dynamically linking to the c lib that would have them. I will defer to @splicemaahs regarding this, but the fix can be carried out in the next release.

• Link to muslc
  • Solution: Add this to dockerfile: RUN mkdir /lib64 && ln -s /lib/libc.musl-x86_64.so.1 /lib64/ld-linux-x86-64.so.2
  • Common approach for Go apps in alpine images, many examples to follow
• Disable cgo
  • Solution: Build command looks like: CGO_ENABLED=0 go build -a -installsuffix cgo -ldflags '-s' src/myapp/myapp.go
  • On non-Linux machines should also specify these build flags: GOOS=linux GOARCH=amd64
  • Can be used for scratch images as well because scratch images have no standard clib, not even muslc.
  • May make binary larger (in terms of single digit MB increases) or slightly decrease performance of network code, but splicectl should be mostly unaffected by these changes.