In my guacd deployment yaml I have:
env:
- name: RECORDING_SEARCH_PATH
value: /var/lib/guacamole/recordings
In my guacamole deployment yaml I have the same:
- name: RECORDING_SEARCH_PATH
value: /var/lib/guacamole/recordings
and for mounting the volume on both containers, I have:
volumeMounts:
- name: guacamole-recordings
mountPath: /var/lib/guacamole/recordings
and
volumes:
- name: guacamole-recordings
persistentVolumeClaim:
claimName: guacamole-recordings
The syntax for kubernetes is a bit different from docker compose, but you
get the idea.
-Aaron
On Mon, Jan 27, 2025 at 3:43 PM Ryan Hall <[email protected]> wrote:
> https://lists.apache.org/thread/d4z1ls3n35z98dmgr59kdvzww3w9z5oh
>
>
>
> I am following this thread and I do not know how to reply to this so here
> it goes…
>
>
>
> I’m wondering if this was ever resolved?
>
>
>
> If someone can point me to a docker-compose.yml for this that would be
> awesome. I am using one that I found and have this exact issue.
>
>
>
> Has anyone tried to mount that folder:
>
>
>
> ./record:/var/lib/guacamole/recordings:rw ß for guacd
>
> ./record:/var/lib/guacamole/recordings:ro ß for gucacamole
>
>
>
> Instead of say ./record:/record which is what the compose file I had came
> with. The problem I had was even if I can change the guacamole.properties
> file, it will be overwritten when updated. Also, there seems to be no text
> editor inside the container when using
>
> docker exec –it docker_compose sh
>
> for example.
>
>
>
> I have a feeling this may have been fixed but somehow whatever I found to
> use is older.
>
>
>
> Thank you,
>
> ____________________________________
>
> Ryan Hall
>
>
>
> Southern Manufacturing Technologies, Inc.
>
> 5910 Johns Road
>
> Tampa, FL 33634
>
>
>
> Phone : (813) 888-8151
>
> Fax : (813) 882-9961
>
> Email : [email protected]
>
>
>
>
>
