Docker image fixes to avoid runtime errors in ubuntu/linux machines

[afsalthaj]

Why now?

I had to do this to try golem as a user before its 1.1 release to see if anything obvious is missing and patch the code straight away. On top of that the main purpose of this PR is as follows:

In case anyone reports issues with 1.1 release, we got this PR to come back to and see if it solves their problem. As discussed within the team, if this doesn't resolve the issue, we will not be spending much time trying to fix it though

Context

This is NOT regarding cross compilation builds or docker-compose builds, but actually running golem docker images in latest ubuntu, and that resulted in incompatibility errors at runtime (which we don't test anywhere). I don't think anyone tested running golem other than Mac (or if at all they ran, it accidentally worked)

I haven't spent much time finding out the right version of ubuntu or the cleanest approach (or the slimmest image with the right version since this task is unplanned), and therefore simply using latest to avoid incompatibility issues.

Find the details, below to get more clarity:

Tests conducted

Environment

Ubuntu with multipass, with the following version

ubuntu@foo:~$ ldd --version
ldd (Ubuntu GLIBC 2.39-0ubuntu8.3) 2.39
Copyright (C) 2024 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Written by Roland McGrath and Ulrich Drepper

Commands Run

cargo make --profile ci build-release with necessary platform overrides, within ubuntu, and then built images with the current docker-files successfully, however simply running any of them failed with lots of errors.

Errors without this change:

Most importantly trying to run them in an ubuntu, resulted in glibc compatibilities (not to mention other errors encountered before narrowing it down to glibc incompatibilities). The cause was Debian slim image was at 2.34 while the required one for our app built in ubuntu-latest needed a specific version.

With the changes in the PR, there are no more runtime issues running golem images in Ubuntu.

[kmatasfp]

not sure if --allow-releaseinfo-change is needed here. Could be be needed if we used pinned version of ubuntu, but as we use ubuntu:latest it will handle the repo information change like suite, codename, version etc and we will be installing from a most up to date repo always. And I do not see us manually adding to/modifying /etc/apt/sources.list which could warrant this option

[afsalthaj]

I think I needed --allow-releaseinfo-change to get something working.

[kmatasfp]

Just verified with fresh ubuntu vm that --allow-releaseinfo-change was not needed, also doing apt-get update twice is not needed, all of this can be replaced with

RUN apt-get update && apt-get install -y libssl-dev ca-certificates

[kmatasfp]

might be worth mentioning that we recommend ubuntu box with following dependencies installed on top of rust toolchain to compile golem:

sudo apt install pkg-config libssl-dev libfontconfig1-dev

As they might use their own tooling to get ubuntu vm (vagrant, https://www.vagrantup.com/, for example is really popular) or already have access to some other ubuntu box

[kmatasfp]

also dependent on you starting point, this might be needed

sudo apt install build-essential

Will get linker 'cc' not found otherwise

[kmatasfp]

Also this

sudo apt-get install protobuf-compiler

[afsalthaj]

@kmatasfp Feel free to raise PRs on what you did on your end to get these things working like https://about.gitea.com/

[kmatasfp]

After you merge this PR I will create a followup PR that describes how to tag and publish built container images to registry, be it self hosted like gitea or dockerhub, github, ecr so you can actually use these built images on your mac which is end goal for most devs