Image Request: Matrix-Synapse-Livekit container

[karmantyu]

I'm not sure if there is any reason behind making a container capable to provide messenger like services for communities. I'm trying to build this function on my FreeBSD server at home, but it is rather complicated for my knowledge to create the co-working jails to do the job. The model is now:

                [ Caddy Reverse Proxy ]
                            /    |    \
      -------- -------     |     ----------------------
     /                           |                                      \

[ matrix_jail ] [ mas_jail ] [ livekit_jail ]

• Synapse (Port 8008) - MAS (Port 8084) - Livekit Server
• PostgreSQL connect - User management - WebRTC (UDP/TCP)

So I do not know if it is doable or it makes any sense at all to make and maintain a container for these services altogether?

[ahze]

Hi,

Good news: this fits the daemonless model well. The key thing is daemonless images are single-service -- we don't bundle everything into one container; each service is its own small OCI image, composed together with compose/appjail-director. So your jail layout maps almost 1:1: matrix_jail --> a Synapse image, mas_jail → a MAS image, livekit_jail → a LiveKit image, plus Postgres and a reverse proxy. Same architecture you have now, just as immutable images.

Where each piece stands:

• PostgreSQL - already done: daemonless/postgres.
• Synapse - very doable. FreeBSD packages it (net-im/py-matrix-synapse, 1.151.0, on Python 3.12), so a daemonless image is a straightforward pkg-based build — no compiling. This is the natural first image and is a working homeserver on its own.
• Reverse proxy - We have daemonless/traefik (& nginx). Caddy should be easy to convert to a container.

I'm not familiar with MAS & LiveKIT, but Go is very portable to FreeBSD.

[karmantyu]

I've Caddy native on my server, servicing all the jails and containers communicating with the world, so I'm not sure if it's need to be in a container. Rather not....
The matrix_jail is up and running nice. It is mainly:

• Matrix Synapse homeserver
• PostgreSQL server
• DragonFly Mail Agent (dma)
• Coturn TURN server

DragonFly is for users if they forgot or want to change passwords.
Coturn is for media transport, e.g. audio/video

After chat is working I realized that Coturn is not enough for the latest clients. Audio and video connections are not working because of some 'sliding protocol' needing for client lookup.
Therefore we need mas_jail which contains:

• Matrix Authentication Service OIDC-based authentication layer for your Matrix Synapse homeserver (compile from GitHUB master!)
• PostgreSQL client
• OPA (Open Policy Agent) WASM

Obviously postgres client is not a challange but I could only set up MAS compiling it from GITHUB master source.
OPA is not an easy thing again, but the jail is up and running.

Now comes livekit_jail which seems to be not an easy task again.

Of course a daemonless image solution would be nice and elegant, not to speak of the necessity caused by the EU Chat Control law coming.