Re: Docker Guacamole Latest

On Wed, Sep 27, 2017 at 7:58 PM, Nick Couchman wrote: > >>> >>> Since 0.9.10-incubating++ appear under guacamole/guacamole it may be >>> worth stripping the same out of glyptodon/guacamole to funnel those like me >>> more directly towards the right answer. >>> >>> >> The

Re: Docker Guacamole Latest

> > >> >> Since 0.9.10-incubating++ appear under guacamole/guacamole it may be >> worth stripping the same out of glyptodon/guacamole to funnel those like me >> more directly towards the right answer. >> >> > The Guacamole project doesn't control whether third parties distribute > their own Docker

Re: Docker Guacamole Latest

On Wed, Sep 27, 2017 at 5:39 PM, Jacob Staub wrote: > Thanks for your patience and assistance. The instruction to inspect the > guacamole containers was the steer I needed. > > Great! > ... > > Since 0.9.10-incubating++ appear under guacamole/guacamole it may be worth >

Re: Docker Guacamole Latest

Thanks for your patience and assistance. The instruction to inspect the guacamole containers was the steer I needed. The problem was traced to an incorrect image identification in the docker-compose file used for the deployment. Incorrect ID: glyptodon/guacamole Corrected ID:

Re: Handling a SAML POST response

On Wed, Sep 27, 2017 at 6:31 PM, Nick Couchman wrote: > > > On Wed, Sep 27, 2017 at 5:35 PM, Colin McGuigan walkingshadows.org> wrote: > >> So I went ahead and created an external web service that internally calls >> /guacamole/api/tokens, and then redirects

Re: Handling a SAML POST response

On Wed, Sep 27, 2017 at 5:35 PM, Colin McGuigan < colin_guacam...@walkingshadows.org> wrote: > So I went ahead and created an external web service that internally calls > /guacamole/api/tokens, and then redirects to /guacamole/#/token= > When you say you created an external web service, what do

Re: Handling a SAML POST response

So I went ahead and created an external web service that internally calls /guacamole/api/tokens, and then redirects to /guacamole/#/token= Doesn't work. Investigation of the network traffic shows that the /guacamole/api/tokens call does not have the token in it at all (in Mike's OpenID

Re: Docker Guacamole Latest

This same issue has been encountered before [1] for an earlier version, but there was no problem with the Guacamole images in that case, and rechecking now things are still correct. The "latest" tag does point to the same image as "0.9.13-incubating", which does contain 0.9.13-incubating:

Re: Docker Guacamole Latest

See attached for the requested output. Regards, Jake On 9/27/2017 12:27 PM, Mike Jumper wrote: On Wed, Sep 27, 2017 at 8:34 AM, Jacob Staub > wrote: Images are were pulled via the Docker Pull Command listed on each corresponding page.

Re: Docker Guacamole Latest

On Wed, Sep 27, 2017 at 8:34 AM, Jacob Staub wrote: > Images are were pulled via the Docker Pull Command listed on each > corresponding page. Example for guacamole: > > docker pull guacamole/guacamole > > Using the above command pulls Tag = latest. I would expect "latest" to

Re: Docker Guacamole Latest

On Wed, Sep 27, 2017 at 11:26 AM, Jacob Staub wrote: > Hello, > > Click here for guacamole. > > Click here for guacd. > > Regards, > Jake > If you look at the Tags tab on both of

Re: Docker Guacamole Latest

Please let us know how/from where you're pulling the image? -Nick On Wed, Sep 27, 2017 at 11:04 AM, Jacob Staub wrote: > Good morning, > > I have been working on updating Docker Guacamole from 0.9.9 to 0.9.13. I > have pulled the latest image for guacamole and guacd. But

Re: Docker Guacamole Latest

Hi Jacob, You are probably pulling the image from the old repository (glyptodon). Verstuurd vanaf mijn iPhone > Op 27 sep. 2017 om 17:04 heeft Jacob Staub het volgende > geschreven: > > Good morning, > > I have been working on updating Docker Guacamole from 0.9.9 to

Docker Guacamole Latest

Good morning, I have been working on updating Docker Guacamole from 0.9.9 to 0.9.13. I have pulled the latest image for guacamole and guacd. But when I deploy Guacamole from the latest images 0.9.11-incubating comes up rather than 0.9.13-incubating. 0.9.11-incubating, or what is indicated on