Publish static landerctl binaries #24

New Issue

Jef Roosens · 2023-11-16T18:40:26+01:00

Jef Roosens commented

2023-11-16 18:40:26 +01:00

We already publish static lander binaries for releases. I'd like to also extend this to landerctl, as this could make it easy to e.g. drop this binary on a server to upload files to the server.

One concern with this is how we would go about packaging libmagic statically, and more specifically the magic.mgc file, which it typically reads from disk.

In order to keep the binary size low, we should build our own version of libcurl that only contains the parts we really need (so just HTTP(S)).

We already publish static `lander` binaries for releases. I'd like to also extend this to `landerctl`, as this could make it easy to e.g. drop this binary on a server to upload files to the server. One concern with this is how we would go about packaging `libmagic` statically, and more specifically the `magic.mgc` file, which it typically reads from disk. In order to keep the binary size low, we should build our own version of libcurl that only contains the parts we really need (so just HTTP(S)).

Jef Roosens added the

Kind/Enhancement

label 2023-11-16 18:40:26 +01:00

Jef Roosens commented

2023-11-17 10:02:16 +01:00

Poster

Building a static package isn't too hard using Alpine Linux, but it seems a static libcurl binary does not necessarily work everywhere. When testing the static binary on the HPC (a Red Hat instance), I get the following error:

Libcurl encountered an error: error setting certificate file: /etc/ssl/certs/ca-certificates.crt

The mentioned file doesn't exist on that system.

Building a static package isn't too hard using Alpine Linux, but it seems a static libcurl binary does not necessarily work everywhere. When testing the static binary on the HPC (a Red Hat instance), I get the following error: ``` Libcurl encountered an error: error setting certificate file: /etc/ssl/certs/ca-certificates.crt ``` The mentioned file doesn't exist on that system.

Jef Roosens commented

2023-11-17 10:50:07 +01:00

Poster

The above problem was easily fixed by allowing the CA certificate file to be configured.

Jef Roosens closed this issue

2023-11-17 14:36:58 +01:00

Sign in to join this conversation.