From: "MeshPoint / Valent Turkovic" <valent@meshpointone.com>
To: "Juliusz Chroboczek" <jch@irif.fr>
Cc: galene@lists.galene.org
Subject: [Galene] Re: Galène docker hub image
Date: Sat, 14 Nov 2026 19:41:43 +0000 [thread overview]
Message-ID: <em75d11789-2ce8-4c34-80b1-a3037efc369a@meshpointone.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1897 bytes --]
Hi Juliusz,
Sorry for the long silence. I wanted to do some testing before replying, but things got busy.
I've actually been running Galène in Docker on my Hetzner server since June, using host networking and a reverse proxy. It's been stable for four and a half months, and I've been using it for regular meetings with two to six people without problems. I haven't collected detailed performance statistics, but if there's something you'd like me to measure, just let me know.
I also ran some networking tests. On a public Linux server with host networking, media connected directly to Galène's UDP ports, with no observed packet loss and RTT between 30 and 44 ms. I haven't found any Galène-specific drawbacks to host networking.
Bridge networking on Docker Desktop for Windows was less straightforward. With only port 8443 published, there was no media. Adding TURN on port 1194 worked, but all media went through TURN. Publishing the UDP range appeared to enable direct connections, but that turned out to be an artifact of the test environment, where clients could reach the container's private address. So your suggestion about advertising external ICE candidates is still relevant.
I also tested Caddy, which worked with proxyURL configured.
I've updated the Dockerfile and README with four deployment examples covering public Linux servers, local servers behind NAT, Docker Desktop on Windows or macOS, and reverse proxies.
https://github.com/valentt/galene/tree/docker/image
I think maintaining one image with a few deployment examples makes more sense than trying to make one configuration work everywhere. It would be useful if others could try it on their own setups and report what works, especially whether media connects directly or through TURN.
I would love for as many people to test in different scenarios and get back their findings...
Valent
[-- Attachment #2: Type: text/html, Size: 2903 bytes --]
next reply other threads:[~2026-11-14 19:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-14 19:41 MeshPoint / Valent Turkovic [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-07-01 22:55 [Galene] Galène docker hub image valent
2026-07-02 10:41 ` [Galene] " Juliusz Chroboczek
2026-07-09 22:28 ` Antonin Décimo
2026-07-10 11:20 ` Valent@MeshPoint
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.galene.org/postorius/lists/galene.lists.galene.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=em75d11789-2ce8-4c34-80b1-a3037efc369a@meshpointone.com \
--to=valent@meshpointone.com \
--cc=galene@lists.galene.org \
--cc=jch@irif.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox