Linkedin bridge breaking with latest bridge-manager container

[dvcrn]

Hi,

the linkedin bridge is currently breaking with the latest bridge-manager container
The issue looks to come from incompatibility between asyncpg and python11+ - MagicStack/asyncpg#1003

      error: command 'gcc' failed: No such file or directory
      [end of output]
  
  note: This error originates from a subprocess, and is likely not a problem with pip.
  ERROR: Failed building wheel for asyncpg
Successfully built linkedin-matrix
Failed to build asyncpg
ERROR: Could not build wheels for asyncpg, which is required to install pyproject.toml-based projects

The latest Dockerfile uses alpine 3.20 which uses python12

I've temporarily fixed this with building a new container that uses an older alpine version with python3 lower than 3.11, eg:

diff --git a/docker/Dockerfile b/docker/Dockerfile
index b90cb6a..ffe2d61 100644
--- a/docker/Dockerfile
+++ b/docker/Dockerfile
@@ -5,7 +5,7 @@ FROM golang:1.22-alpine3.20 AS builder
 COPY . /build/
 RUN cd /build && ./build.sh
 
-FROM alpine:3.20
+FROM alpine:3.17
 
 RUN apk add --no-cache bash curl jq git ffmpeg \
        # Python for python bridges
@@ -14,7 +14,6 @@ RUN apk add --no-cache bash curl jq git ffmpeg \
        py3-magic py3-ruamel.yaml py3-aiohttp py3-pillow py3-olm py3-pycryptodome
 
 COPY --from=lottie /cryptg-*.whl /tmp/
-RUN pip3 install --break-system-packages /tmp/cryptg-*.whl && rm -f /tmp/cryptg-*.whl
 
 COPY --from=builder /build/bbctl /usr/local/bin/bbctl
 COPY --from=lottie /usr/lib/librlottie.so* /usr/lib/

https://hub.docker.com/layers/dvcrn/bridge-manager/alpine3.17/images/sha256-8ca30a9ca03a05b2fe0b799663a11d5495c6af280be6e07574cdeea96977fe36?context=explore