DOC-01: Infrastructure Preparation (Proxmox & Ubuntu)
Initial resource provisioning step in Proxmox VE, Ubuntu Server configuration, and stable Docker engine deployment.
1. Introduction
Sección titulada «1. Introducción»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.
2. Virtual Machine Requirements (Proxmox VE)
Sección titulada «2. Requisitos de la Máquina Virtual (Proxmox VE)»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: hostin 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).
3. Operating System Preparation
Sección titulada «3. Preparación del Sistema Operativo»After completing the base system installation process and establishing secure remote access via SSH, run the described commands to update the system:
3.1. Updates and Security Patches
Sección titulada «3.1. Actualización y Parches de Seguridad»# Actualizar base de datos de paquetes y parches del kernelsudo apt update && sudo apt upgrade -y3.2. Installation of Operational Utilities
Sección titulada «3.2. Instalación de Utilidades de Operación»Install the basic tools required for debugging and editing configurations via the console:
sudo apt install -y curl wget git nano unzip htop4. 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
snapor the default Ubuntu sources is prohibited, as they lack direct compatibility with updated Compose V2 plugins. Follow the official flow:
# 1. Instalar dependencias previas de enrutamiento segurosudo 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 Dockercurl -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 Aptecho "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 modernosudo apt updatesudo apt install -y docker-ce docker-ce-cli containerd.io docker-compose-plugin5. 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:
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.
6. Functional Verification
Sección titulada «6. Verificación de Funcionamiento»Verify that the service is active and the user has full permissions over the local daemon:
docker info# Debería imprimir información de diagnóstico del host sin advertencias de denegación de acceso📊 Host Preparation Checklist
Sección titulada «📊 Checklist de Preparación de Host»- ✓ Allocated Resources: CPU, memory, and disk validation on the Proxmox node.
- ✓ Official Docker: Verification of the
stableinstallation channel against obsolete snap versions. - ✓ Access Security: Console session reload performed to operate the container engine.

