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: guacamole/guacamole
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.
Regards,
Jake
On 9/27/2017 4:32 PM, Mike Jumper wrote:
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:
[mjumper@dev-mjumper ~]$ sudo docker images guacamole/guacamole
REPOSITORY TAG IMAGE ID
CREATED SIZE
docker.io/guacamole/guacamole <http://docker.io/guacamole/guacamole>
0.9.13-incubating b602d8daff1b 11 weeks ago 659.7 MB
docker.io/guacamole/guacamole <http://docker.io/guacamole/guacamole>
latest b602d8daff1b 11 weeks ago 659.7 MB
docker.io/guacamole/guacamole <http://docker.io/guacamole/guacamole>
0.9.12-incubating 9af030afb8c8 6 months ago 651.2 MB
docker.io/guacamole/guacamole <http://docker.io/guacamole/guacamole>
0.9.11-incubating b08c4f8e69f5 8 months ago 650.4 MB
[mjumper@dev-mjumper ~]$ sudo docker images guacamole/guacd
REPOSITORY TAG IMAGE ID
CREATED SIZE
docker.io/guacamole/guacd <http://docker.io/guacamole/guacd>
0.9.13-incubating ac5de9daf9f3 11 weeks ago 499.2 MB
docker.io/guacamole/guacd <http://docker.io/guacamole/guacd> latest
ac5de9daf9f3 11 weeks ago 499.2 MB
docker.io/guacamole/guacd <http://docker.io/guacamole/guacd>
0.9.12-incubating 8e1536c54985 6 months ago 404.9 MB
docker.io/guacamole/guacd <http://docker.io/guacamole/guacd>
0.9.11-incubating 940310c23921 8 months ago 404.5 MB
[mjumper@dev-mjumper ~]$
The output from your run of "docker images" matches, so it looks like
that much is correct on your end, but if you are still seeing 0.9.12
... you must somehow still be pulling an old copy. The string
"0.9.12-incubating" is simply not present in these images. They are
0.9.13.
[mjumper@dev-mjumper ~]$ sudo docker run -it guacamole/guacd
[sudo] password for mjumper:
WARNING: IPv4 forwarding is disabled. Networking will not work.
guacd[1]: INFO:Guacamole proxy daemon (guacd) version
0.9.13-incubating started
guacd[1]: INFO:Listening on host 0.0.0.0, port 4822
(See attached screenshot for guacamole/guacamole version)
If, after retrying, you still see the wrong version, I suggest using
"docker inspect" to verify that the image being used matches the image
ID of 0.9.13-incubating. If it does match, check that your browser
hasn't simply cached the old version.
- Mike
[1]
https://lists.apache.org/thread.html/962d0277242c751786615adbc232f6c669fe842a3465a6331ff4e08c@%3Cuser.guacamole.apache.org%3E
On Wed, Sep 27, 2017 at 10:31 AM, Jacob Staub <[email protected]
<mailto:[email protected]>> wrote:
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 <[email protected]
<mailto:[email protected]>> 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 include 0.9.13-incubating but the suggestion is
that "latest" does not include 0.9.13-incubating.
Please post the output of:
docker images guacamole/guacamole
docker images guacamole/guacd
- Mike
