bitnami / wait-for-port Goto Github PK

Runing executable on Alpine fails:

# ./wait-for-port-linux-amd64 --help
sh: ./wait-for-port-linux-amd64: not found

The same binary run OK on Debian.

Workaround option 1:

apk add gcompat

Workaround option 2:

mkdir /lib64 && ln -s /lib/libc.musl-x86_64.so.1 /lib64/ld-linux-x86-64.so.2

Looks like something with compile options but I'm not a GoLang guy :(

bitnami/wait-for-port version v1.0 has Go version 1.9 which has critical vulnerabilities. The master bitnami/wait-for-port has the version of Go updated to v1.16 which fixes some of the vulnerabilities. change ref :

Can you please create a newer release version with the changes in master.

What is the problem this feature will solve?

People will be able to use the tool without cloning the repo and installing go on their machines, which I'm guessing is a deal breaker for many. I'm considering other options due to this "problem" cause I don't want to install Go tooling on my machine just to use this tool.

What is the feature you are proposing to solve the problem?

Just create binary releases for the 3 major platforms: Linux, Windows and Mac so that people can download the tool and not be forced to build it on their own spending extra time and installing stuff they don't necessarily want or can on their machines.

What alternatives have you considered?

An alternative is to go find an alternative to this tool :)

What is the problem this feature will solve?

AFAICT, bitnami charts and containers files are licensed under Apache2.0. Having the odd GPL'd component makes it more difficult to use the bitnami project.

What is the feature you are proposing to solve the problem?

Re-license under Apache 2.0

What alternatives have you considered?

No response

The current version of the project was built with Go 1.18.2. Binaries created with that version of Go include the following vulnerabilities, some of which are "high" severity making them important to address:

CVE-2022-27664
CVE-2022-28131
CVE-2022-30580
CVE-2022-30630
CVE-2022-30631
CVE-2022-30632
CVE-2022-30633
CVE-2022-30635
CVE-2022-32189

Error returned at compile time