build: bump app base image to fix 'GLIBC_2.34' not found error about teslamate HOT 6 CLOSED

libssl and netcat cause the problems in bookworm, local testing looks promising

from teslamate.

The key issue here is that we use multi stage docker builds (as is recommended practice here). The build one has:

FROM elixir:1.16 AS builder

The final one has:

FROM debian:bookworm-slim AS app
...
RUN apt-get update && apt-get install ...

When you update the build image you also need to update the Debian image and Debian packages to keep them in sync. And determining what versions to use isn't always easy. There could be circumstances where this isn't always the latest Debian version - particularly if you want to build an old version of Teslamate that is based on an older version of elixir.

Yes, building the Docker image from nix would be another solution. Don't think we are quite ready for that though :-)
And I still haven't been able to work out how to use nix in CI yet without slowing the CI down excessively (current pain point where I did this for another project).

from teslamate.

Has been an issue in the past, see

from teslamate.

Nice find, would it make sense to use debian:latest to avoid similar things in the future? Or could that just cause other issues that we never now when it will change?

And we might have new problems with the build due to the new bookworm image:
https://github.com/teslamate-org/teslamate/actions/runs/8054386860

from teslamate.

Nice find, would it make sense to use debian:latest to avoid similar things in the future? Or could that just cause other issues that we never now when it will change?

And we might have new problems with the build due to the new bookworm image:
https://github.com/teslamate-org/teslamate/actions/runs/8054386860

No, good practice is to pin all versions. Best would be to build the docker file with nix, as it would be really reproducible and declarative.

Damn, need more testing

from teslamate.

Closed by 776e7a2 (Typo in referenced issue)

from teslamate.