Install Docmost using Docker on Ubuntu 25.10 to run a collaborative documentation workspace behind HTTPS. With DNS ready, you can reach the setup screen in about 15 minutes.
Ubuntu 25.10 is an interim release that reached end of life in July 2026. This procedure keeps an existing Questing server usable by switching Apt to the archived release, but choose Ubuntu 26.04 LTS for a new production deployment.
Prerequisites
- A 64-bit Ubuntu 25.10 (Questing Quokka) VPS with at least 2 GB of RAM and 10 GB of free disk space. Plan for additional storage if users will upload files.
- SSH access as
root, or a normal Linux account with workingsudoprivileges. - A domain such as
YOUR_DOMAINwith an A record pointing toSERVER_IP. Caddy uses this hostname to issue and renew the TLS certificate. - Inbound TCP ports 80 and 443 allowed by both the VPS provider and the host firewall. Docmost’s application port will stay on loopback.
- A VPSLake Linux VPS if you need an Ubuntu server with root access.
The commands use sudo for a regular SSH account. If you are logged in as root, remove sudo. Ubuntu’s 25.10 release notes document the release’s short support window; do not treat an archived package source as a substitute for security updates.
Step 1: Confirm Questing and repair its archived Apt sources
Why: Ubuntu 25.10 is no longer on the live mirrors, so Apt must use old-releases.ubuntu.com before it can install packages reliably.
Check the release, then change only the standard Ubuntu source file to the archive host. This keeps the source suite as questing instead of mixing packages from another Ubuntu version.
. /etc/os-release
printf '%s\n' "$PRETTY_NAME"
printf 'Codename: %s\n' "$VERSION_CODENAME"
uname -m
sudo sed -i -e 's|archive.ubuntu.com/ubuntu|old-releases.ubuntu.com/ubuntu|g' -e 's|security.ubuntu.com/ubuntu|old-releases.ubuntu.com/ubuntu|g' /etc/apt/sources.list.d/ubuntu.sources
sudo apt-get update
sudo apt-get upgrade -y
The release check should identify Questing and a 64-bit architecture:
Ubuntu 25.10 (Questing Quokka)
Codename: questing
x86_64
If your image stores sources in /etc/apt/sources.list instead, make the same host replacement in that file before rerunning apt-get update. Do not replace questing with noble, jammy, or a Debian suite.
Step 2: Install Docker Engine and Compose
Why: Docker runs the application containers, and the Compose plugin starts Docmost, PostgreSQL, Redis, and Caddy as one stack.
Remove packages that can conflict with Docker’s packages on a fresh VPS. On a host with existing containers, inspect them before removing a runtime package.
sudo apt-get remove -y docker.io docker-compose docker-compose-v2 docker-doc docker-buildx podman-docker containerd runc
sudo apt-get install -y ca-certificates curl openssl
sudo install -m 0755 -d /etc/apt/keyrings
sudo curl -fsSL https://download.docker.com/linux/ubuntu/gpg -o /etc/apt/keyrings/docker.asc
sudo chmod a+r /etc/apt/keyrings/docker.asc
sudo tee /etc/apt/sources.list.d/docker.sources > /dev/null <<EOF
Types: deb
URIs: https://download.docker.com/linux/ubuntu
Suites: questing
Components: stable
Architectures: $(dpkg --print-architecture)
Signed-By: /etc/apt/keyrings/docker.asc
EOF
sudo apt-get update
sudo apt-get install -y docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin
sudo systemctl enable --now docker
This follows Docker’s signed-key repository method from its official Ubuntu installation guide, with the exact questing suite. The guide’s current supported-release list changes after an Ubuntu release reaches end of life, so keep the migration recommendation above in mind.
Check the daemon, Compose plugin, and a disposable container before configuring Docmost:
sudo systemctl is-active docker
sudo docker version --format 'Client {{.Client.Version}} / Server {{.Server.Version}}'
sudo docker compose version
sudo docker run --rm hello-world
Expected output is similar to this; patch numbers vary:
active
Client 29.x.y / Server 29.x.y
Docker Compose version v2.x.y
Hello from Docker!
Keep using sudo docker in this guide. Adding a user to the docker group removes the password prompt but grants that account root-equivalent control of the server.
Step 3: Create Docmost’s protected settings
Why: Docmost needs a long application secret, while PostgreSQL must receive the same database password used in the application’s connection URL.
Generate hexadecimal values so the database password can safely appear in a connection string, then create the deployment directory:
openssl rand -hex 32
openssl rand -hex 24
sudo install -d -m 0750 /opt/docmost
sudo nano /opt/docmost/.env
Enter this in /opt/docmost/.env. Put the first generated value in APP_SECRET, the second in DB_PASSWORD, and replace YOUR_DOMAIN with the hostname users will open:
APP_URL=https://YOUR_DOMAIN
APP_SECRET=REPLACE_WITH_64_HEX_CHARACTERS
DB_PASSWORD=REPLACE_WITH_48_HEX_CHARACTERS
Save the file, then restrict it because it contains a database credential:
sudo chmod 600 /opt/docmost/.env
sudo chown root:root /opt/docmost/.env
The openssl rand -hex 32 command creates 64 characters, exceeding Docmost’s 32-character minimum. APP_URL must exactly match the HTTPS hostname, including a subdomain.
Step 4: Add Caddy and the Compose stack
Why: Caddy obtains HTTPS certificates and forwards WebSocket traffic for real-time editing, while named volumes preserve pages, uploads, database records, Redis data, and certificates.
Create the reverse-proxy configuration with the same hostname used in .env:
sudo nano /opt/docmost/Caddyfile
Paste this content:
YOUR_DOMAIN {
reverse_proxy docmost:3000
}
Now create /opt/docmost/docker-compose.yml:
sudo nano /opt/docmost/docker-compose.yml
Use this definition. The Docmost installation documentation documents these application, PostgreSQL, and Redis settings; the loopback binding below prevents direct public access to port 3000.
services:
caddy:
image: caddy:2
ports:
- "80:80"
- "443:443"
volumes:
- ./Caddyfile:/etc/caddy/Caddyfile:ro
- caddy_data:/data
- caddy_config:/config
depends_on:
- docmost
restart: unless-stopped
docmost:
image: docmost/docmost:latest
depends_on:
- db
- redis
environment:
APP_URL: "${APP_URL}"
APP_SECRET: "${APP_SECRET}"
DATABASE_URL: "postgresql://docmost:${DB_PASSWORD}@db:5432/docmost"
REDIS_URL: "redis://redis:6379"
ports:
- "127.0.0.1:3000:3000"
restart: unless-stopped
volumes:
- docmost:/app/data/storage
db:
image: postgres:18
environment:
POSTGRES_DB: docmost
POSTGRES_USER: docmost
POSTGRES_PASSWORD: "${DB_PASSWORD}"
restart: unless-stopped
volumes:
- db_data:/var/lib/postgresql
redis:
image: redis:8
command: ["redis-server", "--appendonly", "yes", "--maxmemory-policy", "noeviction"]
restart: unless-stopped
volumes:
- redis_data:/data
volumes:
docmost:
db_data:
redis_data:
caddy_data:
caddy_config:
The app, database, and cache communicate over Docker’s private network. Caddy is the only service published on public interfaces, and the named volumes survive a container recreation.
Step 5: Configure UFW and launch Docmost
Why: UFW should allow SSH and Caddy’s web endpoints while leaving the application, PostgreSQL, and Redis inaccessible from the internet.
If SSH uses a custom port, add that port instead of OpenSSH before enabling UFW. Keep your current SSH session open until a second connection succeeds.
sudo apt-get install -y ufw
sudo ufw default deny incoming
sudo ufw default allow outgoing
sudo ufw allow OpenSSH
sudo ufw allow 80/tcp
sudo ufw allow 443/tcp
sudo ufw --force enable
sudo ufw status verbose
The status should show an active firewall and rules for SSH, HTTP, and HTTPS:
Status: active
OpenSSH ALLOW Anywhere
80/tcp ALLOW Anywhere
443/tcp ALLOW Anywhere
Docker can place published ports ahead of some UFW filtering paths. Publishing only Caddy’s ports and binding Docmost to loopback keeps the exposure narrow; apply the same 80/443 policy in the VPS provider firewall.
Validate the rendered Compose file, pull the images, and start the services:
cd /opt/docmost
sudo docker compose config --quiet
sudo docker compose pull
sudo docker compose up -d
sudo docker compose ps
The first pull may take several minutes. A healthy result has four services in an Up state:
NAME SERVICE STATUS PORTS
docmost-caddy-1 caddy Up 0.0.0.0:80->80/tcp, 0.0.0.0:443->443/tcp
docmost-docmost-1 docmost Up 127.0.0.1:3000->3000/tcp
docmost-db-1 db Up
docmost-redis-1 redis Up
Compose may choose different names. A service that repeatedly restarts needs its logs checked before you open the site.
Verify the Docmost installation
Why: The HTTPS health request checks DNS, the provider firewall, UFW, Caddy’s certificate, the proxy route, and Docmost’s listener together.
curl -fsS -o /dev/null -w 'HTTP %{http_code}\n' https://YOUR_DOMAIN/api/health
Expected output:
HTTP 200
Open https://YOUR_DOMAIN in a browser. The Docmost workspace setup page should appear. Enter a workspace name, administrator details, and a unique strong password, then create a page and edit it in a second browser tab to confirm the real-time connection.
Review recent logs after the first login:
cd /opt/docmost
sudo docker compose logs --tail=40 caddy docmost db redis
The output should not show a repeating restart loop, a PostgreSQL authentication error, or an ACME certificate failure.
Troubleshooting
The repository ... questing Release file has expired
The host is still using a live Ubuntu mirror after Questing’s end of life. Reapply the archive-host replacement, then refresh Apt. If the file layout is different, update the matching entries in /etc/apt/sources.list instead.
sudo sed -i -e 's|archive.ubuntu.com/ubuntu|old-releases.ubuntu.com/ubuntu|g' -e 's|security.ubuntu.com/ubuntu|old-releases.ubuntu.com/ubuntu|g' /etc/apt/sources.list.d/ubuntu.sources
sudo apt-get update
Unable to locate package docker-ce
The Docker source is missing, has the wrong suite, or Apt has stale metadata. Confirm the source says Suites: questing, then update the package index and retry the installation:
grep -E '^(URIs|Suites|Architectures|Signed-By):' /etc/apt/sources.list.d/docker.sources
sudo apt-get update
sudo apt-get install -y docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin
Do not change the suite to noble or jammy to work around the error.
Caddy cannot obtain a certificate
The domain may not resolve to SERVER_IP, or port 80/443 may be blocked at the provider firewall. Correct the DNS record, allow both ports, and inspect Caddy’s log:
cd /opt/docmost
sudo docker compose logs --tail=80 caddy
Caddy needs a publicly resolvable hostname for a trusted certificate; an IP address alone is not enough for this setup.
502 Bad Gateway or a restarting Docmost container
The proxy is reachable, but Docmost is not answering on the private network. Check the rendered environment and recent application/database messages, then recreate the services after correcting the missing value:
cd /opt/docmost
sudo docker compose config
sudo docker compose ps
sudo docker compose logs --tail=100 docmost db redis
sudo docker compose up -d
Verify that .env is in /opt/docmost, APP_SECRET is not the placeholder, and DB_PASSWORD matches in the database and DATABASE_URL substitutions.
Hardening and maintenance
- Treat this as a migration deployment: move to Ubuntu 26.04 LTS before the archived Questing packages become a problem.
- Back up the
docmost,db_data, andcaddy_datavolumes before upgrades.docker compose downdoes not remove named volumes unless-vis added. - Keep
/opt/docmost/.envroot-readable only, and update images deliberately withsudo docker compose pull && sudo docker compose up -d. - After confirming SSH access, use the VPSLake UFW firewall generator to review the host rules without opening database or cache ports.
FAQ
Can I run Docmost without a domain?
You can test Docmost at http://127.0.0.1:3000 from the server, but this guide uses Caddy’s automatic HTTPS. A domain gives the workspace a stable APP_URL and lets Caddy request a trusted certificate.
Why does the Compose file use PostgreSQL 18 and Redis 8?
They are the service images in Docmost’s current Docker template. PostgreSQL stores durable workspace data, while Redis supports caching and real-time coordination; neither service needs a public port.
Where does Docmost keep pages and uploaded files?
The docmost named volume is mounted at /app/data/storage, so application files remain when the container is replaced. PostgreSQL data is kept separately in db_data; back up both volumes rather than only the container image.
Should I keep using Ubuntu 25.10 for a public wiki?
No. Questing no longer receives normal security updates, and an archived repository only makes the final packages reachable. Use this page to bridge an existing server, then migrate the stack to Ubuntu 26.04 LTS or another supported release.