Ir al contenido

DOC-01: Infrastructure Preparation (Proxmox & Ubuntu)

Initial resource provisioning step in Proxmox VE, Ubuntu Server configuration, and stable Docker engine deployment.

0views

This technical document establishes the operational directives to provision and parameterize the base operating system (Ubuntu Server) in a virtualized environment on a Proxmox VE hypervisor, preparing the node for the deployment of the Redmine container stack.


When instantiating the virtual machine in the Proxmox administration panel, the following minimum resource limits must be configured to avoid bottlenecks generated by the Ruby on Rails architecture (Redmine's internal engine) and the MySQL database engine:

  • CPU (Processor): 2 high-performance vCPUs (it is suggested to configure Type: host in Proxmox to enable direct translation of physical processor instructions).
  • RAM (Memory): 4 GB minimum (Ruby on Rails consumes considerable memory during static resource compilation).
  • Storage (Disk): 30 GB SSD (or NVMe) with thin provisioning (thin provisioning).
  • Operating System (OS): Ubuntu Server 24.04 LTS or 22.04 LTS (clean installation).

After completing the base system installation process and establishing secure remote access via SSH, run the described commands to update the system:

Ventana de terminal
# Actualizar base de datos de paquetes y parches del kernel
sudo apt update && sudo apt upgrade -y

Install the basic tools required for debugging and editing configurations via the console:

Ventana de terminal
sudo apt install -y curl wget git nano unzip htop

4. Docker Engine Installation (Official Stable Channel)

Sección titulada «4. Instalación de Docker Engine (Canal Oficial Stable)»

[!IMPORTANT] Using the Docker version packaged via snap or the default Ubuntu sources is prohibited, as they lack direct compatibility with updated Compose V2 plugins. Follow the official flow:

Ventana de terminal
# 1. Instalar dependencias previas de enrutamiento seguro
sudo apt install -y apt-transport-https ca-certificates curl software-properties-common gnupg lsb-release
# 2. Añadir la llave criptográfica GPG oficial del registro de Docker
curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo gpg --dearmor -o /usr/share/keyrings/docker-archive-keyring.gpg
# 3. Registrar el repositorio oficial estable en las fuentes de Apt
echo "deb [arch=$(dpkg --print-architecture) signed-by=/usr/share/keyrings/docker-archive-keyring.gpg] https://download.docker.com/linux/ubuntu $(lsb_release -cs) stable" | sudo tee /etc/apt/sources.list.d/docker.list > /dev/null
# 4. Instalar el motor de contenedores y el plugin Compose moderno
sudo apt update
sudo apt install -y docker-ce docker-ce-cli containerd.io docker-compose-plugin

5. Operational Privilege Management (Post-Installation)

Sección titulada «5. Gestión de Privilegios Operativos (Post-Instalación)»

To avoid continuous use of the sudo command when interacting with the Docker socket (mitigating operational risks and simplifying automation), add the system user to the engine group:

Ventana de terminal
sudo usermod -aG docker $USER

[!CAUTION] Mandatory Operational Step: It is strictly necessary to close the active terminal session (exit) and log back into the SSH server to reload the current user's token privileges.


Verify that the service is active and the user has full permissions over the local daemon:

Ventana de terminal
docker info
# Debería imprimir información de diagnóstico del host sin advertencias de denegación de acceso

  • ✓ Allocated Resources: CPU, memory, and disk validation on the Proxmox node.
  • ✓ Official Docker: Verification of the stable installation channel against obsolete snap versions.
  • ✓ Access Security: Console session reload performed to operate the container engine.