Freeradius configuration cannot be stored on a mapped Docker volume

[Alan DeKok]

On Jan 23, 2024, at 1:46 PM, Timothy Weaver <timothyweaver at gmail.com> wrote:
> 
> Actually I was able to get into the container with "docker run --rm -it
> --entrypoint bash freeradius" and then try to manually start the server
> with "freeradius -X". Here's where it dies. The entire /etc/freeradius
> configuration folder is the default files straight from the repository.

  That's a little odd.  It works everywhere else.

> ---- snip ---
> including files in directory /etc/freeradius/policy.d/
> including configuration file /etc/freeradius/policy.d/abfab-tr
> /etc/freeradius/policy.d/abfab-tr[49]: Parse error in condition
> /etc/freeradius/policy.d/abfab-tr[49]: (&GSS-Acceptor-Service-Name &&
> (&outer.request.GSS-Acceptor-Service-Name != &GSS-Acceptor-Servi...
> /etc/freeradius/policy.d/abfab-tr[49]:                                 ^
> Cannot use attribute reference on right side of condition
> Errors reading or parsing /etc/freeradius/radiusd.conf

  The short answer is that if you're not using the abfab-tr policy, then just delete that file.

  Alan DeKok.