Is this from a git bisect? - Mike
On Mon, Aug 2, 2021, 13:59 Leo Nikolaev <[email protected]> wrote: > Okay, I’ve done some triaging by building and checking manually some > commits. > > Commit 037ed21 is definetely okay, and it even has the logout support, so > fits perfectly. > > There is a bunch of commits at 8th of July then, and the last of them, > dd86130 is completely broken. > > Commit cc239b6e has the bug with Safari. > > So I think bug was introduced somewhere at 8th of July, will try to test > more commits. > > Cheers, > Leo > > > On 30 Jul 2021, at 04:00, Mike Jumper <[email protected]> wrote: > > > > On Wed, Jul 28, 2021 at 3:36 AM Leo Nikolaev <[email protected]> > wrote: > > If comfortable, I can record a screencast or do a Zoom demo of what am I > doing. > > > > I’m absolutely sure about latest master - I mount it inside > Docker-container, and when I remove -v parameter it all works perfectly on > 1.3.0. > > > > docker run --name guacamole \ > > --link guacd \ > > --link mysql \ > > -v $(pwd)/guacamole:/etc/guacamole \ > > -v > $(pwd)/guacamole-client/guacamole/target/guacamole-1.3.0.war:/opt/guacamole/guacamole.war > \ > > -e MYSQL_DATABASE=guacamole \ > > -e MYSQL_USER=root \ > > -e MYSQL_PASSWORD=guacamole \ > > -e GUACAMOLE_HOME=/etc/guacamole \ > > -d -p 8080:8080 \ > > guacamole/guacamole > > > > Building it from repo, yes. > > > > Manually layering an externally-built, newer .war file over the .war > within the Docker image from a previous release is a bit funky. To ensure > things are sane, can you build the Docker image directly from the same > source and get rid of the volume mount? The Dockerfile for the image is > part of the guacamole-client repository, so you can just do a "docker > build" from the root of the source that you cloned from git to produce an > updated image. > > > > Thanks, > > > > Michael Jumper > > CEO, Lead Developer > > Glyptodon Inc. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
