{"id":1123,"date":"2026-11-19T13:00:00","date_gmt":"2026-11-19T13:00:00","guid":{"rendered":"https:\/\/vpslake.com\/blog\/?p=1123"},"modified":"2026-11-19T13:00:00","modified_gmt":"2026-11-19T13:00:00","slug":"install-docmost-docker-ubuntu-25-10","status":"publish","type":"post","link":"https:\/\/vpslake.com\/blog\/2026\/11\/19\/install-docmost-docker-ubuntu-25-10\/","title":{"rendered":"How to Install Docmost Using Docker on Ubuntu 25.10"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">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.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">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.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Prerequisites<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n\n<li>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.<\/li>\n\n\n<li>SSH access as <code>root<\/code>, or a normal Linux account with working <code>sudo<\/code> privileges.<\/li>\n\n\n<li>A domain such as <code>YOUR_DOMAIN<\/code> with an A record pointing to <code>SERVER_IP<\/code>. Caddy uses this hostname to issue and renew the TLS certificate.<\/li>\n\n\n<li>Inbound TCP ports 80 and 443 allowed by both the VPS provider and the host firewall. Docmost&#8217;s application port will stay on loopback.<\/li>\n\n\n<li>A <a href=\"https:\/\/vpslake.com\/buy-vps\">VPSLake Linux VPS<\/a> if you need an Ubuntu server with root access.<\/li>\n\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">The commands use <code>sudo<\/code> for a regular SSH account. If you are logged in as <code>root<\/code>, remove <code>sudo<\/code>. Ubuntu&#8217;s <a href=\"https:\/\/documentation.ubuntu.com\/release-notes\/25.10\/\" target=\"_blank\" rel=\"noopener\">25.10 release notes<\/a> document the release&#8217;s short support window; do not treat an archived package source as a substitute for security updates.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 1: Confirm Questing and repair its archived Apt sources<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Why: Ubuntu 25.10 is no longer on the live mirrors, so Apt must use <code>old-releases.ubuntu.com<\/code> before it can install packages reliably.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Check the release, then change only the standard Ubuntu source file to the archive host. This keeps the source suite as <code>questing<\/code> instead of mixing packages from another Ubuntu version.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>. \/etc\/os-release\nprintf '%s\\n' \"$PRETTY_NAME\"\nprintf 'Codename: %s\\n' \"$VERSION_CODENAME\"\nuname -m\nsudo 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\nsudo apt-get update\nsudo apt-get upgrade -y<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">The release check should identify Questing and a 64-bit architecture:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>Ubuntu 25.10 (Questing Quokka)\nCodename: questing\nx86_64<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">If your image stores sources in <code>\/etc\/apt\/sources.list<\/code> instead, make the same host replacement in that file before rerunning <code>apt-get update<\/code>. Do not replace <code>questing<\/code> with <code>noble<\/code>, <code>jammy<\/code>, or a Debian suite.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 2: Install Docker Engine and Compose<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Why: Docker runs the application containers, and the Compose plugin starts Docmost, PostgreSQL, Redis, and Caddy as one stack.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Remove packages that can conflict with Docker&#8217;s packages on a fresh VPS. On a host with existing containers, inspect them before removing a runtime package.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo apt-get remove -y docker.io docker-compose docker-compose-v2 docker-doc docker-buildx podman-docker containerd runc\nsudo apt-get install -y ca-certificates curl openssl\nsudo install -m 0755 -d \/etc\/apt\/keyrings\nsudo curl -fsSL https:\/\/download.docker.com\/linux\/ubuntu\/gpg -o \/etc\/apt\/keyrings\/docker.asc\nsudo chmod a+r \/etc\/apt\/keyrings\/docker.asc\nsudo tee \/etc\/apt\/sources.list.d\/docker.sources &gt; \/dev\/null &lt;&lt;EOF\nTypes: deb\nURIs: https:\/\/download.docker.com\/linux\/ubuntu\nSuites: questing\nComponents: stable\nArchitectures: $(dpkg --print-architecture)\nSigned-By: \/etc\/apt\/keyrings\/docker.asc\nEOF\nsudo apt-get update\nsudo apt-get install -y docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin\nsudo systemctl enable --now docker<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">This follows Docker&#8217;s signed-key repository method from its <a href=\"https:\/\/docs.docker.com\/engine\/install\/ubuntu\/\" target=\"_blank\" rel=\"noopener\">official Ubuntu installation guide<\/a>, with the exact <code>questing<\/code> suite. The guide&#8217;s current supported-release list changes after an Ubuntu release reaches end of life, so keep the migration recommendation above in mind.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Check the daemon, Compose plugin, and a disposable container before configuring Docmost:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo systemctl is-active docker\nsudo docker version --format 'Client {{.Client.Version}} \/ Server {{.Server.Version}}'\nsudo docker compose version\nsudo docker run --rm hello-world<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Expected output is similar to this; patch numbers vary:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>active\nClient 29.x.y \/ Server 29.x.y\nDocker Compose version v2.x.y\nHello from Docker!<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Keep using <code>sudo docker<\/code> in this guide. Adding a user to the <code>docker<\/code> group removes the password prompt but grants that account root-equivalent control of the server.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 3: Create Docmost&#8217;s protected settings<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Why: Docmost needs a long application secret, while PostgreSQL must receive the same database password used in the application&#8217;s connection URL.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Generate hexadecimal values so the database password can safely appear in a connection string, then create the deployment directory:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>openssl rand -hex 32\nopenssl rand -hex 24\nsudo install -d -m 0750 \/opt\/docmost\nsudo nano \/opt\/docmost\/.env<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Enter this in <code>\/opt\/docmost\/.env<\/code>. Put the first generated value in <code>APP_SECRET<\/code>, the second in <code>DB_PASSWORD<\/code>, and replace <code>YOUR_DOMAIN<\/code> with the hostname users will open:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>APP_URL=https:\/\/YOUR_DOMAIN\nAPP_SECRET=REPLACE_WITH_64_HEX_CHARACTERS\nDB_PASSWORD=REPLACE_WITH_48_HEX_CHARACTERS<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Save the file, then restrict it because it contains a database credential:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo chmod 600 \/opt\/docmost\/.env\nsudo chown root:root \/opt\/docmost\/.env<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">The <code>openssl rand -hex 32<\/code> command creates 64 characters, exceeding Docmost&#8217;s 32-character minimum. <code>APP_URL<\/code> must exactly match the HTTPS hostname, including a subdomain.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 4: Add Caddy and the Compose stack<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">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.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Create the reverse-proxy configuration with the same hostname used in <code>.env<\/code>:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo nano \/opt\/docmost\/Caddyfile<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Paste this content:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>YOUR_DOMAIN {\n    reverse_proxy docmost:3000\n}<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Now create <code>\/opt\/docmost\/docker-compose.yml<\/code>:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo nano \/opt\/docmost\/docker-compose.yml<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Use this definition. The <a href=\"https:\/\/docmost.com\/docs\/installation\" target=\"_blank\" rel=\"noopener\">Docmost installation documentation<\/a> documents these application, PostgreSQL, and Redis settings; the loopback binding below prevents direct public access to port 3000.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>services:\n  caddy:\n    image: caddy:2\n    ports:\n      - \"80:80\"\n      - \"443:443\"\n    volumes:\n      - .\/Caddyfile:\/etc\/caddy\/Caddyfile:ro\n      - caddy_data:\/data\n      - caddy_config:\/config\n    depends_on:\n      - docmost\n    restart: unless-stopped\n\n  docmost:\n    image: docmost\/docmost:latest\n    depends_on:\n      - db\n      - redis\n    environment:\n      APP_URL: \"${APP_URL}\"\n      APP_SECRET: \"${APP_SECRET}\"\n      DATABASE_URL: \"postgresql:\/\/docmost:${DB_PASSWORD}@db:5432\/docmost\"\n      REDIS_URL: \"redis:\/\/redis:6379\"\n    ports:\n      - \"127.0.0.1:3000:3000\"\n    restart: unless-stopped\n    volumes:\n      - docmost:\/app\/data\/storage\n\n  db:\n    image: postgres:18\n    environment:\n      POSTGRES_DB: docmost\n      POSTGRES_USER: docmost\n      POSTGRES_PASSWORD: \"${DB_PASSWORD}\"\n    restart: unless-stopped\n    volumes:\n      - db_data:\/var\/lib\/postgresql\n\n  redis:\n    image: redis:8\n    command: [\"redis-server\", \"--appendonly\", \"yes\", \"--maxmemory-policy\", \"noeviction\"]\n    restart: unless-stopped\n    volumes:\n      - redis_data:\/data\n\nvolumes:\n  docmost:\n  db_data:\n  redis_data:\n  caddy_data:\n  caddy_config:<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">The app, database, and cache communicate over Docker&#8217;s private network. Caddy is the only service published on public interfaces, and the named volumes survive a container recreation.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 5: Configure UFW and launch Docmost<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Why: UFW should allow SSH and Caddy&#8217;s web endpoints while leaving the application, PostgreSQL, and Redis inaccessible from the internet.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If SSH uses a custom port, add that port instead of <code>OpenSSH<\/code> before enabling UFW. Keep your current SSH session open until a second connection succeeds.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo apt-get install -y ufw\nsudo ufw default deny incoming\nsudo ufw default allow outgoing\nsudo ufw allow OpenSSH\nsudo ufw allow 80\/tcp\nsudo ufw allow 443\/tcp\nsudo ufw --force enable\nsudo ufw status verbose<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">The status should show an active firewall and rules for SSH, HTTP, and HTTPS:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>Status: active\nOpenSSH                  ALLOW       Anywhere\n80\/tcp                   ALLOW       Anywhere\n443\/tcp                  ALLOW       Anywhere<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Docker can place published ports ahead of some UFW filtering paths. Publishing only Caddy&#8217;s ports and binding Docmost to loopback keeps the exposure narrow; apply the same 80\/443 policy in the VPS provider firewall.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Validate the rendered Compose file, pull the images, and start the services:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>cd \/opt\/docmost\nsudo docker compose config --quiet\nsudo docker compose pull\nsudo docker compose up -d\nsudo docker compose ps<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">The first pull may take several minutes. A healthy result has four services in an <code>Up<\/code> state:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>NAME                 SERVICE   STATUS    PORTS\ndocmost-caddy-1      caddy     Up        0.0.0.0:80-&gt;80\/tcp, 0.0.0.0:443-&gt;443\/tcp\ndocmost-docmost-1    docmost   Up        127.0.0.1:3000-&gt;3000\/tcp\ndocmost-db-1         db        Up\ndocmost-redis-1      redis     Up<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Compose may choose different names. A service that repeatedly restarts needs its logs checked before you open the site.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Verify the Docmost installation<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Why: The HTTPS health request checks DNS, the provider firewall, UFW, Caddy&#8217;s certificate, the proxy route, and Docmost&#8217;s listener together.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>curl -fsS -o \/dev\/null -w 'HTTP %{http_code}\\n' https:\/\/YOUR_DOMAIN\/api\/health<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Expected output:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>HTTP 200<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Open <code>https:\/\/YOUR_DOMAIN<\/code> 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.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Review recent logs after the first login:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>cd \/opt\/docmost\nsudo docker compose logs --tail=40 caddy docmost db redis<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">The output should not show a repeating restart loop, a PostgreSQL authentication error, or an ACME certificate failure.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Troubleshooting<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\"><code>The repository ... questing Release file has expired<\/code><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The host is still using a live Ubuntu mirror after Questing&#8217;s end of life. Reapply the archive-host replacement, then refresh Apt. If the file layout is different, update the matching entries in <code>\/etc\/apt\/sources.list<\/code> instead.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>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\nsudo apt-get update<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\"><code>Unable to locate package docker-ce<\/code><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The Docker source is missing, has the wrong suite, or Apt has stale metadata. Confirm the source says <code>Suites: questing<\/code>, then update the package index and retry the installation:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>grep -E '^(URIs|Suites|Architectures|Signed-By):' \/etc\/apt\/sources.list.d\/docker.sources\nsudo apt-get update\nsudo apt-get install -y docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Do not change the suite to <code>noble<\/code> or <code>jammy<\/code> to work around the error.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Caddy cannot obtain a certificate<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The domain may not resolve to <code>SERVER_IP<\/code>, or port 80\/443 may be blocked at the provider firewall. Correct the DNS record, allow both ports, and inspect Caddy&#8217;s log:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>cd \/opt\/docmost\nsudo docker compose logs --tail=80 caddy<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Caddy needs a publicly resolvable hostname for a trusted certificate; an IP address alone is not enough for this setup.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><code>502 Bad Gateway<\/code> or a restarting Docmost container<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">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:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>cd \/opt\/docmost\nsudo docker compose config\nsudo docker compose ps\nsudo docker compose logs --tail=100 docmost db redis\nsudo docker compose up -d<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Verify that <code>.env<\/code> is in <code>\/opt\/docmost<\/code>, <code>APP_SECRET<\/code> is not the placeholder, and <code>DB_PASSWORD<\/code> matches in the database and <code>DATABASE_URL<\/code> substitutions.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Hardening and maintenance<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n\n<li>Treat this as a migration deployment: move to Ubuntu 26.04 LTS before the archived Questing packages become a problem.<\/li>\n\n\n<li>Back up the <code>docmost<\/code>, <code>db_data<\/code>, and <code>caddy_data<\/code> volumes before upgrades. <code>docker compose down<\/code> does not remove named volumes unless <code>-v<\/code> is added.<\/li>\n\n\n<li>Keep <code>\/opt\/docmost\/.env<\/code> root-readable only, and update images deliberately with <code>sudo docker compose pull &amp;&amp; sudo docker compose up -d<\/code>.<\/li>\n\n\n<li>After confirming SSH access, use the <a href=\"https:\/\/vpslake.com\/ufw-firewall-generator\">VPSLake UFW firewall generator<\/a> to review the host rules without opening database or cache ports.<\/li>\n\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">FAQ<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Can I run Docmost without a domain?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">You can test Docmost at <code>http:\/\/127.0.0.1:3000<\/code> from the server, but this guide uses Caddy&#8217;s automatic HTTPS. A domain gives the workspace a stable <code>APP_URL<\/code> and lets Caddy request a trusted certificate.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Why does the Compose file use PostgreSQL 18 and Redis 8?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">They are the service images in Docmost&#8217;s current Docker template. PostgreSQL stores durable workspace data, while Redis supports caching and real-time coordination; neither service needs a public port.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Where does Docmost keep pages and uploaded files?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The <code>docmost<\/code> named volume is mounted at <code>\/app\/data\/storage<\/code>, so application files remain when the container is replaced. PostgreSQL data is kept separately in <code>db_data<\/code>; back up both volumes rather than only the container image.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Should I keep using Ubuntu 25.10 for a public wiki?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">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.<\/p>\n\n\n\n<aside class=\"vl-element vl-cta-banner\" aria-label=\"Host Docmost securely\">\n\t<div class=\"vl-cta-banner__content\">\n\t\t<p class=\"vl-cta-banner__eyebrow\">Ubuntu VPS<\/p>\n\t\t<h3 class=\"vl-cta-banner__title\">Host Docmost securely<\/h3>\n\t\t<p class=\"vl-cta-banner__text\">Deploy a Docker-based documentation workspace on a root-access Ubuntu VPS with HTTPS-ready networking.<\/p>\n\t<\/div>\n\t<a class=\"vl-cta-banner__button\" href=\"\/buy-vps\" aria-label=\"View Linux VPS plans\">View Linux VPS plans<\/a>\n<\/aside>\n\n\n\n<script type=\"application\/ld+json\">{\"@context\": \"https:\/\/schema.org\", \"@type\": \"FAQPage\", \"mainEntity\": [{\"@type\": \"Question\", \"name\": \"Can I run Docmost without a domain?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"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.\"}}, {\"@type\": \"Question\", \"name\": \"Why does the Compose file use PostgreSQL 18 and Redis 8?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"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.\"}}, {\"@type\": \"Question\", \"name\": \"Where does Docmost keep pages and uploaded files?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"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.\"}}, {\"@type\": \"Question\", \"name\": \"Should I keep using Ubuntu 25.10 for a public wiki?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"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.\"}}]}<\/script>\n\n","protected":false},"excerpt":{"rendered":"Install Docmost using Docker on Ubuntu 25.10 with Caddy HTTPS, PostgreSQL, Redis, UFW, health checks, and fixes for a private wiki in about 15 minutes.","protected":false},"author":1,"featured_media":1124,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"csco_singular_sidebar":"","csco_page_header_type":"","csco_page_load_nextpost":"","footnotes":""},"categories":[5,9],"tags":[118,138,139,103],"class_list":["post-1123","post","type-post","status-publish","format-standard","has-post-thumbnail","category-guides","category-vps-hosting","tag-docker","tag-docmost","tag-self-hosting","tag-ubuntu-25-10","cs-entry"],"_links":{"self":[{"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/posts\/1123","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/comments?post=1123"}],"version-history":[{"count":1,"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/posts\/1123\/revisions"}],"predecessor-version":[{"id":4111,"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/posts\/1123\/revisions\/4111"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/media\/1124"}],"wp:attachment":[{"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/media?parent=1123"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/categories?post=1123"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/tags?post=1123"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}