Hi Nick,
thanks for your answer.
I basically followed this chapter and adapted it for docker:
https://guacamole.apache.org/doc/gug/radius-auth.html
I used the given mvn-command on the checked-out repo to create a guacamole-auth-radius-1.1.0.jar which I added to the container's extension directory. I also had to disable javadoc as otherwise mvn gave me errors while compiling. I don't think that matters.
On start of the container, docker logs tells me that the Radius-extension is "not compatible with this version of Guacamole" so I thought that the docker-image might be too old. Now, you tell me, that there is no 1.1.0 but what else could be the issue?
Best wishes
Michael
Gesendet: Dienstag, 20. August 2019 um 18:18 Uhr
Von: "Nick Couchman" <[email protected]>
An: [email protected]
Betreff: Re: docker-container for Guacamole 1.1.0
Von: "Nick Couchman" <[email protected]>
An: [email protected]
Betreff: Re: docker-container for Guacamole 1.1.0
On Tue, Aug 20, 2019 at 5:13 AM "michael böhm" <[email protected]> wrote:
Hi everyone,is there already a date for the container on docker-hub being updated to the newest version?
No, 1.1.0 has not been released, yet, so there is no Docker image published.
Alternatively, is there a way to build it by myself?
Yes - the Dockerfile files are part of the source code - you can check out the source code and run "docker build" from within the source directory.
Background: I have compiled the radius-plugin with version 1.1.0 which does not work on the "latest"-container from docker-hub.
First, there really is no version 1.1.0, yet, although there's a staging directory where we are assembling code for 1.1.0. Additionally the master branch of the repo uses version 1.1.0 at present, so it's hard to know what version you're actually downloading and compiling. Second, "does not work" is a rather vague problem description - against what RADIUS server(s) have you tried, with what RADIUS protocols, and what errors are you seeing? I'm happy to work to help track down the issue, or advise if it's an issue that's already been resolved, but we need a little more information to go on than this.
-Nick
