fix: build container beside amd64 also for ARM

[genofire]

i also update base-container from rust:buster to rust:bookworm - we have to test the new libssl before release it

---

hate github - where is my checkbox, that this MergeRequest has to squash-merge ?

[p1gp1g]

I've started to move mollysocket to mollyim organisation !

I have edited the container recently, it may help : mollyim/mollysocket@c8fc7aa

[genofire]

there appears a 404, i am not able to see that repo.

cool that it merged clother together :)

[p1gp1g]

Indeed it is in private, I m asking to change the visibility :)

The commit does that :

-    apt install -y libssl1.1 libsqlite3-0
+    apt install -y openssl libssl-dev ca-certificates libssl1.1 libsqlite3-0

[p1gp1g]

I'm merging it, I will add it to the other repo when the visibility changes.

BTW:

• It would be nice to upload the builds on releases
• About the helm repo, do you prefer we move it to mollyim org or to your own profile (then we will refer it in MollySocket's readme) ? I guess MollySocket org will be closed

[genofire]

i believe it would be nice, to have that next to or in mollysocket.
so maybe the https://github.com/mollyim/mollysocket-helm whould be nice.

---

oh yes, but i do not know yet how. normally i would use semantic-release (on gitlab, but also work on github).

It is possible to select there assets which are uploaded, too.
but therefore automatically create release based on convention-commits and could/should not use any manualle release or version-tagging.
If you like it, i will develop an github-workflow for release

i start something here #20