RE: Help with Freeradius/freeradius-server Docker Container
Just tried it. Seems to work. You are right in that it does not show much log information, but you can check whether the server is running by executing "ps auxw" inside the container
docker exec -ti my-radius ps aux
That's kind of the problem.. The docker container starts and immediately dies so I can't connect to the container. I DID run in debug mode with -X at the end as was suggested. The container still starts and immediately exits. 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 " It's as if something is already bound to port 1812 within the container. There are no other radius services running on the docker host This docker host is ubuntu 18.04. As a test, I tried to load the container on my synology NAS and it DOES start up with no problem using the same command as above. Not sure what's misconfigured on my ubuntu system. Any ideas/assistance are appreciated.
On Mar 11, 2019, at 4:55 PM, Reuben Fischman <Fischmanr@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.
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@lists.freeradius.org> on behalf of Alan DeKok <aland@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@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://nam01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.freeradius.org%2Flist%2Fusers.html&data=02%7C01%7C%7C4cee88e5e65a49c34d6f08d6a667ac93%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636879361530985020&sdata=qvbxkqr5ifcJuEidvZV070ad1BWKKmldidEfI4MIdVM%3D&reserved=0
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@lists.freeradius.org> on behalf of Reuben Fischman <Fischmanr@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@lists.freeradius.org> on behalf of Alan DeKok <aland@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@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
On Mar 12, 2019, at 6:54 AM, Reuben Fischman <Fischmanr@outlook.com> wrote:
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.
Yes. The default FreeRADIUS configuration uses IPv6. Alan DeKok.
On Tue, 2019-03-12 at 10:54 +0000, Reuben Fischman wrote:
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.
OK, thanks. I've not seen a system without IPv6 for several years. Certainly didn't check that when building the images. The whole idea with the Docker images is you provide your own config - the default one won't be of much use to many people. So this really is "if you run without IPv6, use a FreeRADIUS config without IPv6". -- Matthew
I've not seen a system without IPv6 for several years. Certainly didn't check that when building the images. Sadly not having IPv6 is not as un-common for docker hosts as you might think. In part because its default setup doesn't configure IPv6 (or didn't the last time I looked at a new clean install). -- A. Information in this email including any attachments may be privileged, confidential and is intended exclusively for the addressee. The views expressed may not be official policy, but the personal views of the originator. If you have received it in error, please notify the sender by return e-mail and delete it from your system. You should not reproduce, distribute, store, retransmit, use or disclose its contents to anyone. Please note we reserve the right to monitor all e-mail communication through our internal and external networks. SKY and the SKY marks are trademarks of Sky Limited and Sky International AG and are used under licence. Sky UK Limited (Registration No. 2906991), Sky-In-Home Service Limited (Registration No. 2067075), Sky Subscribers Services Limited (Registration No. 2340150) and Sky CP Limited (Registration No. 9513259) are direct or indirect subsidiaries of Sky Limited (Registration No. 2247735). All of the companies mentioned in this paragraph are incorporated in England and Wales and share the same registered office at Grant Way, Isleworth, Middlesex TW7 5QD
On Tue, 2019-03-12 at 11:47 +0000, Winfield, Alister via Freeradius- Users wrote:
I've not seen a system without IPv6 for several years. Certainly didn't check that when building the images.
Sadly not having IPv6 is not as un-common for docker hosts as you might think. In part because its default setup doesn't configure IPv6 (or didn't the last time I looked at a new clean install).
Fair enough. Maybe they should consider joining the 21st century :) The Docker images use the default config, so it would be no different than simply installing FreeRADIUS directly on the host. You'd have to fix up the config in either case. -- Matthew
participants (4)
-
Alan DeKok -
Matthew Newton -
Reuben Fischman -
Winfield, Alister