Collabora Online - Built-in CODE Server on proxmox¶

The problem I was encountering is related to the restricted access to cryptographic resources such as /dev/random and /dev/urandom inside a Docker container, and also was the proble in a Proxmox Container

These resources are essential for generating random numbers and ensuring the security of various cryptographic operations within applications and services.

Solution Attempt 1 (Docker Container): Initially, I attempted to address the problem by modifying the Docker container settings. I added permissions for device nodes like /dev/random and /dev/urandom within the Docker container, as these permissions are essential for certain Collabora Online features to work correctly. However, this approach did not resolve the issue, and I continued to face the same error.

Solution Attempt 2 - Running Collabora Online in a Native Proxmox Container (CT) with Permissions:

In an effort to address issues with Collabora Online within Proxmox, I chose a different approach:

Native CT Installation:

Instead of using a Docker container or a VM, I set up Collabora Online within a Proxmox container (CT) using a native installation.
This direct installation within the CT allowed for precise configuration.
Adding CT Permissions:

To ensure that the CT had the necessary permissions for certain features of Collabora Online, I modified the Proxmox container (CT) configuration file:
Location: /etc/pve/nodes/<nodename>/lxc/<container_id>.conf
I added these lines to the configuration file:

lxc.cgroup.devices.allow = c 1:8 rwm
lxc.cgroup.devices.allow = c 1:9 rwm

These lines granted the CT the capability to create and manage device nodes, including /dev/random and /dev/urandom.
This approach allowed Collabora Online to function smoothly within the Proxmox environment, resolving the encountered issues.

Solution Attempt 3 (Native Install in a VM): To overcome the limitations and difficulties I faced with the Docker container setup, I decided to perform a native installation of Collabora Online within a virtual machine (VM). This involved creating a dedicated VM, installing Collabora Online directly within the VM, and configuring it to work with my Nextcloud server. This approach proved successful, and I was able to use Collabora Online without encountering the error.