Help with Freeradius/freeradius-server Docker Container

[Reuben Fischman]

> SO that puts a new twist.  I don't have IPv6 enabled on the docker host, and its a default installation of docker so IPv6 shouldn't be enabled.  This container is the default container downloaded form the hub with no changes made.  If IPv6 isn't supported, why is it trying to listen on something that isn't configured?

An update on this issue..  I got the container to start up and have been able to test with it.  The issue wasn't to DISABLE IPv6, but rather to ENABLE IPv6 on the Docker host.  once I re-enabled IPv6, it worked just fine.
________________________________
From: Freeradius-Users <freeradius-users-bounces+fischmanr=outlook.com at lists.freeradius.org> on behalf of Reuben Fischman <Fischmanr at outlook.com>
Sent: Monday, March 11, 2019 7:45 PM
To: FreeRadius users mailing list
Subject: Re: Help with Freeradius/freeradius-server Docker Container

> That's the real problem.  The docker container doesn't support IPv6.
>
 > If you don't need IPv6, edit the configuration so that it doesn't listen on IPv6 addresses.

SO that puts a new twist.  I don't have IPv6 enabled on the docker host, and its a default installation of docker so IPv6 shouldn't be enabled.  This container is the default container downloaded form the hub with no changes made.  If IPv6 isn't supported, why is it trying to listen on something that isn't configured?

________________________________
From: Freeradius-Users <freeradius-users-bounces+fischmanr=outlook.com at lists.freeradius.org> on behalf of Alan DeKok <aland at deployingradius.com>
Sent: Monday, March 11, 2019 5:22 PM
To: FreeRadius users mailing list
Subject: Re: Help with Freeradius/freeradius-server Docker Container


> On Mar 11, 2019, at 4:55 PM, Reuben Fischman <Fischmanr at outlook.com> wrote:
> I DID run in debug mode with -X at the end as was suggested.  The container still starts and immediately exits.

  Reading the debug output helps.  Also, describing the actual problem helps.

> Command I'm executing is:
> "docker run --name my-radius -d freeradius/freeradius-server -X"
>
> After the container dies, I run a "docker container logs my-radius" and get a fair amount of output as the container goes through the startup process.  It ends with the following lines:
> "Failed opening auth address :: port 1812 bound to server default: Address family not supported by protocol
> /etc/freeradius/sites-enabled/default[245]: Error binding to port for :: port 1812

  That's the real problem.  The docker container doesn't support IPv6.

  If you don't need IPv6, edit the configuration so that it doesn't listen on IPv6 addresses.

  Alan DeKok.


-
List info/subscribe/unsubscribe? See https://nam05.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.freeradius.org%2Flist%2Fusers.html&data=02%7C01%7C%7C61690940e4e44c2cec6508d6a67bc4ca%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636879447839431658&sdata=PyHLezjmjZSOERz%2B9VwCn9jr72UvpWmTjh8daqCFsVE%3D&reserved=0
-
List info/subscribe/unsubscribe? See https://nam05.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.freeradius.org%2Flist%2Fusers.html&data=02%7C01%7C%7C61690940e4e44c2cec6508d6a67bc4ca%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636879447839441705&sdata=qZ%2FjAAka70XsZyJwnhdd3TUJ1YdvRDdkF9JPVRJqVT8%3D&reserved=0