Does not work on alpine (linking issue?)

[jakub-bochenski]

$ docker run --rm -it alpine sh
/ # wget https://github.com/CycloneDX/sbom-utility/releases/download/v0.18.1/sbom-utility-v0.18.1-linux-amd64.tar.gz
Connecting to github.com (140.82.121.4:443)
Connecting to release-assets.githubusercontent.com (185.199.108.133:443)
saving to 'sbom-utility-v0.18.1-linux-amd64.tar.gz'
sbom-utility-v0.18.1 100% |**************************************************************************************************************************************************************************************| 7939k  0:00:00 ETA
'sbom-utility-v0.18.1-linux-amd64.tar.gz' saved
/ # mkdir tools
/ #  tar -xz -C tools < 'sbom-utility-v0.18.1-linux-amd64.tar.gz'
/ # ls tools
LICENSE                        README.md                      config.json                    custom.json                    license.json                   sbom-utility                   sbom-utility-v0.18.1.bom.json
/ # tools/sbom-utility
sh: tools/sbom-utility: not found
/ # 

[jakub-bochenski]

/ # ldd tools/sbom-utility
        /lib64/ld-linux-x86-64.so.2 (0x7f708b875000)
Error loading shared library libresolv.so.2: No such file or directory (needed by tools/sbom-utility)
        libpthread.so.0 => /lib64/ld-linux-x86-64.so.2 (0x7f708b875000)
        libc.so.6 => /lib64/ld-linux-x86-64.so.2 (0x7f708b875000)

[jakub-bochenski]

apk add gcompat fixes it would be nice if this was documented

[mrutkows]

@jakub-bochenski Apart from compiling with LLVM, I have no way to test the resultant binaries on different Linux distros. Feel free to contribute to the docs. under the "Troubleshooting" section of the README to help others ;)

[jakub-bochenski]

There is no "Troubleshooting" section there now, should I add it?

[jakub-bochenski]

Maybe just add it to "Running", like the MacOs thing?

[mrutkows]

There is no "Troubleshooting" section there now, should I add it?

@jakub-bochenski yes, please feel free to add anything you feel would help someone on other platforms under a new Troubleshooting section at the end of the README.md file.

Also, sorry for the much delayed response; my "day job" has kept me busy with working on ML Model tooling.