Hi! I'm looking into using the `guaclog` utility in a dockerized setup. guaclog is part of the "guacamole-server" or guacd codebase. This is the tool that can extract keypresses from a recording into a plain text file.
However, it looks like in the Dockerfile, in the build steps, guaclog is explicitly excluded from in the guacd Docker image, so I can't just do something like: docker exec guacd_compose guaclog /path/to/recording As a test, I built my own docker image, changing GUACAMOLE_SERVER_OPTS to remove the --disable-guaclog, and after that, I can use a container running from this image to run guacd. Or I can just docker run this new image to just get guaclog. But IMO, just using exec into the guacd container is easier because the /record path is already mapped into the container. (If it wasn't, guacd couldn't write the recording to start with.) So, for now, I'm ending up building my own Docker image for guacd just so that guaclog is not excluded, which isn't really great as a long-term solution. Before I suggest to stop excluding guaclog from the guacd Docker images, I'd like to ask the mailing list, is there a better way of doing this? --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscr...@guacamole.apache.org For additional commands, e-mail: user-h...@guacamole.apache.org
