Anyone else's Guacamole instance stop working after the latest container image update?

[tehniemer]

I tried to access my instance this morning and was greeted with a 404, checked the logs and found this:

s
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ss ht syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon rep_good nopl xtopology cpuid tsc_known_freq pni pclmulqdq vmx ssse3 fma cx16 pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand hypervisor lahf_lm abm cpuid_fault invpcid_single pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid xsaveopt arat umip md_clear arch_capabilities
vmx flags	: vnmi preemption_timer invvpid ept_x_only ept_ad ept_1gb flexpriority tsc_offset vtpr mtf vapic ept vpid unrestricted_guest shadow_vmcs pml
bugs		: cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs srbds
bogomips	: 6800.00
clflush size	: 64
cache_alignment	: 64
address sizes	: 39 bits physical, 48 bits virtual
power management:

processor	: 3
vendor_id	: GenuineIntel
cpu family	: 6
model		: 60
model name	: Intel(R) Xeon(R) CPU E3-1231 v3 @ 3.40GHz
�
stepping	: 3
microcode	: 0x27
cpu MHz		: 3400.000
cache size	: 16384 KB
physical id	: 0
�
siblings	: 4
�
core id		: 3
cpu cores	: 4
apicid		: 3
initial apicid	: 3
fpu		: yes
fpu_exception	: yes
cpuid level	: 13
�



Memory: 4k page, physical 16393028k(467588k free), swap 0k(0k free)

vm_info: OpenJDK 64-Bit Server VM (25.332-b09) for linux-amd64 JRE (1.8.0_332-b09), built on Apr 22 2022 17:20:05 by "jenkins" with gcc 7.5.0

time: Wed Jun 29 15:23:01 2022
timezone: UTC
elapsed time: 0.008101 seconds (0d 0h 0m 0s)

Anyone know what's going on here?

[tehniemer]

Nevermind, seems that I just needed to upgrade docker and mariadb to the latest versions.