Hey guys, I'm following this thread as I have to setup session recording on either docker or k8s setup. So, we need to mount /var/lib/guacamole/recordings directory on both guacd and guacamole container. How can we manage cross permissions on both containers? Documentation seems a bit vague.
Thanks, Raj Burnwal Get Outlook for Android<https://aka.ms/AAb9ysg> ________________________________ From: Nick Couchman <[email protected]> Sent: Friday, May 26, 2023 5:53:02 PM To: [email protected] <[email protected]> Cc: Golota S.V. <[email protected]>; Michael Jumper <[email protected]> Subject: Re: Configuring connections to use recording storage for docker version On Fri, May 26, 2023 at 6:40 AM Golota S.V. <[email protected]> wrote: after reading the manual many times, I came to the conclusion that there is no mention of recording-search-path in the docker-compose.yml file, but I did not find the syntax for entering it, I think that by default there is no place in the container for storing and indexing recording files. in some places it is mentioned that you need to enable EXTENSIONS: history-recording-storage and specify the path for storing recording-search-path: /var/lib/guacamole/recordings can you tell me how to do it right? attempting to display the file /home/guacamole/.guacamole/guacamole.properties from the container for editing did not work. Yep, you are correct, the option for the recording storage path is not available in the Docker startup script. Sorry we missed that earlier - we'll need to put in a Jira ticket and change to add that option to the startup. Regarding the guacamole.properties file, most likely it is in /etc/guacamole in the container, as that's the default GUACAMOLE_HOME location. -NIck CAUTION: This email was sent from an external source. This is not an Opcito User. Be cautious while downloading any attachments and clicking on links. The content of this email is confidential and intended for the recipient specified in the message only. It is strictly forbidden to share any part of this message with any third party without the written consent of the sender. If you received this message by mistake, please reply to this message and follow with its deletion so that we can ensure such a mistake does not occur in the future.
