Hi Paul, Since you are the second to report encountering this, and since you are using a fresh VM, I wonder if perhaps Docker Hub is having some sort of issues with caching and serving older Docker images.
I just now reconfirmed for "guacamole/guacd" (after manually removing the existing local copies of the images, and then manually pulling them again) that the contents of the images are correct builds of the 0.9.12-incubating release: [mjumper@dev-mjumper ~]$ sudo docker run --rm -it guacamole/guacd:0.9.12-incubating guacd[1]: INFO: Guacamole proxy daemon (guacd) version 0.9.12-incubating started guacd[1]: INFO: Listening on host 0.0.0.0, port 4822 [mjumper@dev-mjumper ~]$ sudo docker run --rm -it guacamole/guacd guacd[1]: INFO: Guacamole proxy daemon (guacd) version 0.9.12-incubating started guacd[1]: INFO: Listening on host 0.0.0.0, port 4822 [mjumper@dev-mjumper ~]$ sudo docker run --rm -it guacamole/guacd:latest guacd[1]: INFO: Guacamole proxy daemon (guacd) version 0.9.12-incubating started guacd[1]: INFO: Listening on host 0.0.0.0, port 4822 If you're still seeing 0.9.11-incubating, the only possibility is that you must somehow have a copy of the older image. I'm not sure how this is possible, but since Docker Hub does have the correct images, it's the only conclusion. Could your VM be using a mirror of some sort? Thanks, - Mike On Thu, Apr 20, 2017 at 3:33 PM, Paul Azad <[email protected]> wrote: > Hi > > > > I just pulled down guacamole/guacamole & guacamole/guacd on a new linux VM > i spun up to do some Docker/Guacamole testing. > > > > Guacamole web looks to be v0.9.12: > > http://XXX.XXX.XXX.XXX:8080/guacamole/app.js?v=0.9.12-incubating > > > > But guacd is 0.9.11: > > root@docker01:~# docker logs docker-guacd > > guacd[1]: INFO: Guacamole proxy daemon (guacd) version 0.9.11-incubating > started > > guacd[1]: INFO: Listening on host 0.0.0.0, port 4822 > > > > > > Thanks > > > > > > *From:* Mike Jumper [mailto:[email protected]] > *Sent:* Wednesday, 5 April 2017 1:33 AM > *To:* [email protected] > *Subject:* Re: Latest docker images still appear to be 0.9.11-incubating > > > > On Tue, Apr 4, 2017 at 8:12 AM, Falklian <[email protected]> > wrote: > > I am running guacamole and guacd using Docker. This morning, I pulled the > latest images for each and rebuilt my containers. After messing around > with > guacamole a bit, I noticed that the new favicons weren't working. Upon > viewing page source, I noticed that the CSS and JavaScript links still > pointed to 0.9.11-incubating. I removed the containers/images and > specifically pulled 0.9.12-incubating and now the favicons are working. > > Looks like the Docker images may have been built against 0.9.11-incubating > > > > Hi Falkian, > > > > I just rechecked the guacamole/guacamole [1] and guacamole/guacd [2] > Docker images, and they were both correctly built against > 0.9.12-incubating. If you were still seeing the 0.9.11-incubating version, > then you must either have still somehow been using the older images, or the > older version must have been cached by the browser. The new images do > indeed contain the new version. > > > > - Mike > > > > [1] https://hub.docker.com/r/guacamole/guacamole/ > <https://contactmonkey.com/api/v1/tracker?cm_session=8536d624-7d84-413c-aa8e-c9c096eef61d&cm_type=link&cm_link=c5079d6d-5d0f-45fc-91f9-eff8a2c27d2c&cm_destination=https://hub.docker.com/r/guacamole/guacamole/> > > [2] https://hub.docker.com/r/guacamole/guacd/ > <https://contactmonkey.com/api/v1/tracker?cm_session=8536d624-7d84-413c-aa8e-c9c096eef61d&cm_type=link&cm_link=20936d98-ae67-4022-9c5d-b261648d1367&cm_destination=https://hub.docker.com/r/guacamole/guacd/> > > > > [image: > https://contactmonkey.com/api/v1/tracker?cm_session=8536d624-7d84-413c-aa8e-c9c096eef61d&cm_type=open&[email protected]] >
