How to run Podman and Dockge in an Alpine LXC on Proxmox

Date: 2023-11-26


I just want to run containers on Proxmox in a maintainable way.

How should a solution look?

Why Dockge? Dockge simplifies the most tedious parts of containers: creation, execution, and navigation. I also appreciate how it exposes all the most important info without extra clicks. It’s a very new project, so I don’t know what else to expect, but I also don’t mind running an occasional podman command to do other stuff.

Why not Yacht? Yacht did seem to work with Docker, but its UI moves around too much for me. Its disappearing menus and scrollbars make me lose focus.

Why not Portainer? Portainer introduced a distracting advertisement for its Business Edition earlier this year. It became less obnoxious after 6 months, but it’s clear that the project cannot exist as purely open source.

Why not Kubernetes? I’d like to, but Minikube and K3s complain about Cgroups.

Why not in a VM? If RAM wasn’t a concern, I would have used a virtual machine like the Proxmox admin guide recommends for application containers. Though I must admit that LXCs and ZFS filesystems are more accessible than VMs and ZFS volumes.


Before continuing, I should note a few non-standard decisions with my setup:


In Proxmox, download an Alpine “CT Template” and then “Create CT” with it. There’s nothing particularly special in the creation process.


Boot into the new Alpine LXC and run the following commands.

# Testing repository is required for podman-compose.
echo '' >> /etc/apk/repositories
apk update
apk upgrade
apk add fuse-overlayfs podman-docker podman-compose
# Ensure Podman uses fuse-overlayfs.
sed -i -e 's:.*mount_program *=.*:mount_program = "/usr/bin/fuse-overlayfs":' /etc/containers/storage.conf
# Always start Podman on boot.
rc-update add podman boot
# We updated a lot. Get a fresh boot.


After rebooting into the Alpine LXC, create a Dockge compose.yaml file and run it with the following commands. It differs from the default compose.yaml in the ways mentioned earlier.

mkdir -p /opt/compose/dockge

cat >/opt/compose/dockge/compose.yaml <<HERE
version: "3"
    driver: local
    name: "dockge_data"
    image: louislam/dockge:1
    restart: always
      # Host Port : Container Port
      - 5001:5001
      - /var/run/podman/podman.sock:/var/run/docker.sock
      - dockge_data:/app/data
      - /opt/compose:/opt/compose
      - DOCKGE_STACKS_DIR=/opt/compose

cd /opt/compose/dockge
podman-compose up -d


That’s it. Dockge should now be accessible on port 5001. If you want a simple test, use the following YAML file to set up a stack. It just prints a version number and exits.

# This file is /opt/compose/fildesh_oneoff/compose.yaml
# if you name the stack "fildesh_oneoff".
version: "3"
    restart: no
    command: --version