Re: Docker Container 2.5.0 / roundup_healthcheck

SCHLEMMER Norbert <[email protected]> Mon, 27 Oct 2025 16:26:35 +0000
Newsgroups gmane.comp.bug-tracking.roundup.user
Message-ID <DU2PR01MB8557A2ECCC91D3E795179441E8FCA@DU2PR01MB8557.eurprd01.prod.exchangelabs.com>
If GNU wget is used instead of BusyBox, wget can be restricted to IP v4.
wget -4 -q -O /dev/null http://localhost:8080/

Or simply use 127.0.0.1 for health checks in the container

Br
Norbert


-----Urspr=FCngliche Nachricht-----
Von: Ralf Schlatterbeck <[email protected]> =

Gesendet: Montag, 27. Oktober 2025 16:25
An: [email protected]
Betreff: Re: [Roundup-users] Docker Container 2.5.0 / roundup_healthcheck

*EXTERNAL source*


On Mon, Oct 27, 2025 at 02:49:55PM +0000, SCHLEMMER Norbert wrote:
> Hello All
>
> Running the Rundup Docker container 2.5.0-1 with Debian 13 / Trixie as =

> host
>
> There seems to be a problem with the roundup_healthcheck script using =

> localhost

This looks like localhost on your machine maps to both, 127.0.0.1 and
::1 (IPv4 and IPv6). But it seems the roundup-server is listening only on t=
he IPv4 address.

Maybe you can fix it by making localhost only an ipv4 address and have a se=
parate name for ipv6 localhost.

e.g. in /etc/hosts:

127.0.0.1  localhost
::1        ip6-localhost ip6-loopback

I'm not familiar with the container setup...

Kind regards
Ralf
--
Dr. Ralf Schlatterbeck                  Tel:   +43/2243/26465-16
Open Source Consulting                  www:   www.runtux.com
Reichergasse 131, A-3411 Weidling       email: [email protected]


_______________________________________________
Roundup-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/roundup-users