Testing Scripts

​

Testing Environment

​

Requirements

• Proxmox VE 8.0+ - Supported versions: 8.0-8.9, 9.0-9.1
• Sufficient storage - At least 50GB free for testing
• Network access - Internet connectivity for downloading packages
• Test VM/Container IDs - Use high numbers (e.g., 900+) to avoid conflicts

​

Testing Container Scripts

​

Basic Testing Workflow

bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/docker.sh)"

bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/docker.sh)"
# Select: Advanced Installation
# Verify all 19 configuration steps work

# Enter container
pct enter CTID

# Check service status
systemctl status appname

# Verify application responds
curl http://localhost:8080

# From Proxmox host
bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/docker.sh)"
# Script should detect existing container and offer update

pct stop CTID
pct destroy CTID

​

Testing Install Scripts

​

Manual Testing

# Create a test container
pct create 999 /var/lib/vz/template/cache/debian-12-standard_12.7-1_amd64.tar.zst \
  --hostname test-container \
  --memory 2048 \
  --cores 2 \
  --rootfs local-lvm:8 \
  --net0 name=eth0,bridge=vmbr0,ip=dhcp \
  --unprivileged 1

# Start container
pct start 999

# Wait for container to boot
sleep 5

# Execute install script
pct exec 999 bash < install/docker-install.sh

# Verify installation
pct exec 999 systemctl status docker

# Clean up
pct stop 999
pct destroy 999

​

Testing with Different OS Versions

# Debian 12 (Bookworm)
var_os="debian"
var_version="12"

# Debian 13 (Trixie)
var_os="debian"
var_version="13"

# Ubuntu 22.04 LTS
var_os="ubuntu"
var_version="22.04"

# Ubuntu 24.04 LTS
var_os="ubuntu"
var_version="24.04"

# Alpine 3.20
var_os="alpine"
var_version="3.20"

# Alpine 3.21
var_os="alpine"
var_version="3.21"

​

Testing VM Scripts

​

Basic VM Testing

bash vm/haos-vm.sh
# Choose: Default Settings

# List VMs
qm list

# Check VM configuration
qm config VMID

# Monitor VM boot
qm terminal VMID

# Wait for VM to boot (30-60 seconds)
sleep 60

# Check VM status
qm status VMID

# Get VM IP (if QEMU guest agent is running)
qm guest cmd VMID network-get-interfaces

qm stop VMID
qm destroy VMID

​

Automated Testing

​

Test Script Template

#!/usr/bin/env bash

set -e

SCRIPT_NAME="docker"
TEST_CTID=999

echo "Testing ct/${SCRIPT_NAME}.sh..."

# Cleanup function
cleanup() {
  if pct status $TEST_CTID &>/dev/null; then
    echo "Cleaning up test container..."
    pct stop $TEST_CTID 2>/dev/null || true
    pct destroy $TEST_CTID 2>/dev/null || true
  fi
}

trap cleanup EXIT

# Run script with default settings (non-interactive)
echo "Running container creation..."
var_ctid=$TEST_CTID bash ct/${SCRIPT_NAME}.sh <<EOF

EOF

# Verify container was created
if ! pct status $TEST_CTID &>/dev/null; then
  echo "FAIL: Container was not created"
  exit 1
fi

echo "SUCCESS: Container created"

# Verify container is running
if ! pct status $TEST_CTID | grep -q "running"; then
  echo "FAIL: Container is not running"
  exit 1
fi

echo "SUCCESS: Container is running"

# Enter container and verify service
if ! pct exec $TEST_CTID systemctl is-active docker &>/dev/null; then
  echo "FAIL: Docker service is not running"
  exit 1
fi

echo "SUCCESS: Docker service is running"

# Test update script
echo "Testing update function..."
var_ctid=$TEST_CTID bash ct/${SCRIPT_NAME}.sh <<EOF

EOF

echo "SUCCESS: All tests passed"

​

Running Automated Tests

# Make test script executable
chmod +x test-container-script.sh

# Run tests
./test-container-script.sh

​

Common Test Cases

​

Container Script Tests

# Test with minimal resources
var_cpu="1" var_ram="512" var_disk="2" bash ct/app.sh

# Test with maximum resources
var_cpu="8" var_ram="8192" var_disk="50" bash ct/app.sh

​

Install Script Tests

# Test verbose mode
VERBOSE="yes" pct exec CTID bash < install/app-install.sh

# Test with custom variables
APP="MyApp" RELEASE="v1.2.3" pct exec CTID bash < install/app-install.sh

​

Update Function Tests

# Test update with existing version file
echo "v1.0.0" | pct push CTID - /opt/app_version.txt
var_ctid=CTID bash ct/app.sh  # Should detect update available

# Test update when already latest
echo "v2.0.0" | pct push CTID - /opt/app_version.txt
var_ctid=CTID bash ct/app.sh  # Should report no update needed

​

Validation Checklist

​

Before Submitting

​

Container Scripts (ct/)

• Script runs successfully with default settings
• Script runs successfully with advanced (19-step) settings
• Container starts and application is accessible
• Service starts on container boot (systemctl enable)
• Update function detects and applies updates
• Update function reports “no update” when current
• Tested on target OS (Debian/Ubuntu/Alpine)
• Resources (CPU/RAM/Disk) are appropriate
• Container is unprivileged unless privileged is required
• No errors in container logs (journalctl -xe)

​

Install Scripts (install/)

• Script completes without errors
• All dependencies install successfully
• Application downloads and extracts correctly
• Configuration files are created with correct permissions
• Services start successfully
• Version file created in /opt/${APP}_version.txt
• Cleanup runs successfully (no leftover temp files)
• Works with both verbose and silent modes
• Handles errors gracefully with msg_error

​

VM Scripts (vm/)

• VM creates successfully with default settings
• VM creates successfully with advanced settings
• VM boots successfully (within 2 minutes)
• Network configuration works (IP assigned)
• Cloud-init runs successfully (if applicable)
• QEMU guest agent reports status
• Disk size is appropriate for OS
• VM uses q35 machine type (unless i440fx required)
• EFI boot works correctly
• Image download and extraction succeed

​

Debugging Failed Tests

​

Container Creation Fails

# Check Proxmox logs
tail -f /var/log/pve/tasks/active

# Check container creation logs
pct config CTID

# Check container console
pct console CTID

# Check container logs
pct exec CTID journalctl -xe

​

Service Won’t Start

# Check service status
pct exec CTID systemctl status appname

# Check service logs
pct exec CTID journalctl -u appname -n 50

# Check application logs
pct exec CTID cat /var/log/appname/error.log

​

Network Issues

# Check network configuration
pct config CTID | grep net0

# Test network from container
pct exec CTID ping -c 3 8.8.8.8
pct exec CTID curl -I https://google.com

# Check DNS
pct exec CTID cat /etc/resolv.conf

​

Update Function Fails

# Check version file
pct exec CTID cat /opt/app_version.txt

# Test GitHub API manually
curl -fsSL https://api.github.com/repos/user/repo/releases/latest

# Check update script logic
pct exec CTID bash -x < ct/app.sh  # Run with debug mode

​

Performance Testing

​

Resource Usage

# Monitor container resources
pct status CTID --verbose

# Check CPU usage
pct exec CTID top -bn1 | head -20

# Check memory usage
pct exec CTID free -h

# Check disk usage
pct exec CTID df -h

​

Load Testing

# Test application under load
ab -n 1000 -c 10 http://container-ip:8080/

# Monitor during load
watch -n 1 'pct status CTID --verbose'

​

Best Practices

​

DO:

• Test on clean Proxmox installation - Avoid pre-configured environments
• Use high container/VM IDs for testing - e.g., 900+ to avoid conflicts
• Test all installation modes - Default, Advanced, User Defaults
• Verify cleanup works - No leftover files, containers, or VMs
• Test update function thoroughly - Both “update available” and “up to date” scenarios
• Document any special requirements - GPU passthrough, kernel modules, etc.
• Test on minimum supported Proxmox version - PVE 8.0+

​

DON’T:

• Test in production environments
• Skip advanced installation mode testing
• Forget to test the update function
• Leave test containers/VMs running
• Assume it works on all OS versions without testing
• Ignore error messages or warnings
• Submit untested code

​

Continuous Integration

name: Test Container Scripts

on:
  pull_request:
    paths:
      - 'ct/**'
      - 'install/**'

jobs:
  test:
    runs-on: self-hosted  # Proxmox runner
    steps:
      - uses: actions/checkout@v3
      
      - name: Test container creation
        run: |
          ./tests/test-container-script.sh ${{ matrix.script }}
        
      - name: Cleanup
        if: always()
        run: |
          ./tests/cleanup.sh
    
    strategy:
      matrix:
        script:
          - docker
          - pihole
          - homeassistant

​

Reporting Issues

1. Proxmox version: pveversion
2. Script name and version: ct/app.sh or vm/os-vm.sh
3. Installation mode: Default/Advanced/etc.
4. Error messages: Full error output
5. Container/VM logs: journalctl -xe, systemctl status
6. Steps to reproduce: Exact commands used

Title: Docker container creation fails on Proxmox 8.2

Environment:
- Proxmox VE: 8.2.1
- Script: ct/docker.sh
- Mode: Default installation

Error:

Steps to reproduce:
1. Run: bash ct/docker.sh
2. Select: Default installation
3. Error occurs during Docker installation

Logs: