Issues with very old libssl shared library not being found

[dehuszar]

I added this trigger to a project I am working on. My OS is Ubuntu 24.04, and was seeing the following error:

Finished building all Spin components
/home/sam/.local/share/spin/plugins/trigger-cron/trigger-cron: error while loading shared libraries: libssl.so.1.1: cannot open shared object file: No such file or directory
Logging component stdio to ".spin/logs/"
Storing default SQLite data to ".spin/sqlite_db.db"

Serving http://127.0.0.1:3000
Available Routes:
  rss-reader: http://127.0.0.1:3000 (wildcard)
A trigger exited unexpectedly. Terminating.

Current versions of Ubuntu are using libssl v3. Tracking down an old version from archived repos does resolve the issue, but I suspect on enough people's machines, doing so will result in some kind of unexpected side-effect.

[itowlson]

@karthik2804 I see spin trigger http loads but trigger-cron doesn't, even though both are built on Ubuntu 20. Spin sets --features openssl/vendored on all Ubuntu builds but cron only sets it on aarch64 which I think is why cron is hitting this...?

https://github.com/fermyon/spin/blob/2a9bf7c57eda9aa42152f016373d3105170b164b/.github/workflows/release.yml#L34

vs

https://github.com/fermyon/spin-trigger-cron/blob/c62cb5012f53b5a1c5765192bd227b826f9aa6d4/.github/workflows/build.yaml#L26

[karthik2804]

@itowlson could very well be the case, I will update the action. I think this is common across all our triggers - if it fixes the issue here, I can update the rest as well.

[itowlson]

Sounds good @karthik2804 - thanks!