Operating system: Debian Linux 13
Webmin version: 2.670
Virtualmin version: 8.3.0 Professional
I deploy Discourse using the recipe. If Debian has GRUB_CMDLINE_LINUX="ipv6.disable=1", then:
Checking deployment requirements ..
.. done
Creating pod discourse ..
.. done
Creating container discourse-db from docker.io/discourse/postgres:pg17 ..
.. done
Waiting for discourse-db to become ready ..
.. done
Creating container discourse-redis from docker.io/library/redis:7-alpine ..
.. done
Waiting for discourse-redis to become ready ..
.. done
Creating container discourse-web from docker.io/discourse/discourse:latest ..
.. done
Waiting for discourse-web to become ready ..
.. failed : container discourse-web did not become ready: curl: (7) Failed to connect to 127.0.0.1 port 80 after 0 ms: Could not connect to server
After some timeout it returns the message:
The failed deployment was rolled back. Its containers, pod, proxy configuration, and newly created persistent storage were removed. Downloaded images were kept in the image cache for future deployments.
Deployment log:
a85eb871d7ae 1:C 24 Oct 2026 14:43:26.292 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can also cause failures without low memory condition, see https://github.com/jemalloc/jemalloc/issues/1328. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
a85eb871d7ae 1:C 24 Oct 2026 14:43:26.292 * oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
a85eb871d7ae 1:C 24 Oct 2026 14:43:26.292 * Redis version=7.4.11, bits=64, commit=00000000, modified=0, pid=1, just started
a85eb871d7ae 1:C 24 Oct 2026 14:43:26.292 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
a85eb871d7ae 1:M 24 Oct 2026 14:43:26.293 * monotonic clock: POSIX clock_gettime
a85eb871d7ae 1:M 24 Oct 2026 14:43:26.295 * Running mode=standalone, port=6379.
a85eb871d7ae 1:M 24 Oct 2026 14:43:26.297 # Warning: Could not create server TCP listening socket ::*:6379: unable to bind socket, errno: 97
a85eb871d7ae 1:M 24 Oct 2026 14:43:26.298 * Server initialized
a85eb871d7ae 1:M 24 Oct 2026 14:43:26.300 * Ready to accept connections tcp
5efd9ee0a7da The files belonging to this database system will be owned by user "postgres".
5efd9ee0a7da This user must also own the server process.
5efd9ee0a7da
5efd9ee0a7da The database cluster will be initialized with locale "en_US.utf8".
5efd9ee0a7da The default database encoding has accordingly been set to "UTF8".
5efd9ee0a7da The default text search configuration will be set to "english".
5efd9ee0a7da
5efd9ee0a7da Data page checksums are disabled.
5efd9ee0a7da
5efd9ee0a7da fixing permissions on existing directory /var/lib/postgresql/17/docker ... ok
5efd9ee0a7da creating subdirectories ... ok
5efd9ee0a7da selecting dynamic shared memory implementation ... posix
5efd9ee0a7da selecting default "max_connections" ... 100
5efd9ee0a7da selecting default "shared_buffers" ... 128MB
5efd9ee0a7da selecting default time zone ... Etc/UTC
5efd9ee0a7da creating configuration files ... ok
5efd9ee0a7da running bootstrap script ... ok
5efd9ee0a7da performing post-bootstrap initialization ... ok
5efd9ee0a7da syncing data to disk ... ok
5efd9ee0a7da
5efd9ee0a7da
5efd9ee0a7da Success. You can now start the database server using:
5efd9ee0a7da
5efd9ee0a7da pg_ctl -D /var/lib/postgresql/17/docker -l logfile start
5efd9ee0a7da
5efd9ee0a7da initdb: warning: enabling "trust" authentication for local connections
5efd9ee0a7da initdb: hint: You can change this by editing pg_hba.conf or using the option -A, or --auth-local and --auth-host, the next time you run initdb.
5efd9ee0a7da waiting for server to start....2026-10-24 14:43:23.558 UTC [48] LOG: starting PostgreSQL 17.11 (Debian 17.11-1.pgdg12+2) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14+deb12u1) 12.2.0, 64-bit
5efd9ee0a7da 2026-10-24 14:43:23.559 UTC [48] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
5efd9ee0a7da 2026-10-24 14:43:23.562 UTC [51] LOG: database system was shut down at 2026-10-24 14:43:23 UTC
5efd9ee0a7da 2026-10-24 14:43:23.564 UTC [48] LOG: database system is ready to accept connections
5efd9ee0a7da done
5efd9ee0a7da server started
5efd9ee0a7da CREATE DATABASE
5efd9ee0a7da
5efd9ee0a7da
5efd9ee0a7da /usr/local/bin/docker-entrypoint.sh: running /docker-entrypoint-initdb.d/bootstrap-db.sh
5efd9ee0a7da CREATE ROLE
5efd9ee0a7da GRANT
5efd9ee0a7da ALTER SCHEMA
5efd9ee0a7da ALTER ROLE
5efd9ee0a7da CREATE EXTENSION
5efd9ee0a7da CREATE EXTENSION
5efd9ee0a7da CREATE EXTENSION
5efd9ee0a7da ALTER EXTENSION
5efd9ee0a7da NOTICE: version "0.8.6" of extension "vector" is already installed
5efd9ee0a7da CREATE EXTENSION
5efd9ee0a7da CREATE EXTENSION
5efd9ee0a7da CREATE EXTENSION
5efd9ee0a7da ALTER EXTENSION
5efd9ee0a7da NOTICE: version "0.8.6" of extension "vector" is already installed
5efd9ee0a7da
5efd9ee0a7da /usr/local/bin/docker-entrypoint.sh: running /docker-entrypoint-initdb.d/configure-postgres.sh
5efd9ee0a7da
5efd9ee0a7da waiting for server to shut down....2026-10-24 14:43:23.905 UTC [48] LOG: received fast shutdown request
5efd9ee0a7da 2026-10-24 14:43:23.906 UTC [48] LOG: aborting any active transactions
5efd9ee0a7da 2026-10-24 14:43:23.908 UTC [48] LOG: background worker "logical replication launcher" (PID 54) exited with exit code 1
5efd9ee0a7da 2026-10-24 14:43:23.908 UTC [49] LOG: shutting down
5efd9ee0a7da 2026-10-24 14:43:23.909 UTC [49] LOG: checkpoint starting: shutdown immediate
5efd9ee0a7da 2026-10-24 14:43:23.923 UTC [49] LOG: checkpoint complete: wrote 1150 buffers (7.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.011 s, sync=0.003 s, total=0.015 s; sync files=366, longest=0.002 s, average=0.001 s; distance=6228 kB, estimate=6228 kB; lsn=0/1AFC068, redo lsn=0/1AFC068
5efd9ee0a7da 2026-10-24 14:43:23.926 UTC [48] LOG: database system is shut down
5efd9ee0a7da done
5efd9ee0a7da server stopped
5efd9ee0a7da
5efd9ee0a7da PostgreSQL init process complete; ready for start up.
5efd9ee0a7da
5efd9ee0a7da 2026-10-24 14:43:24.023 UTC [1] LOG: starting PostgreSQL 17.11 (Debian 17.11-1.pgdg12+2) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14+deb12u1) 12.2.0, 64-bit
5efd9ee0a7da 2026-10-24 14:43:24.025 UTC [1] LOG: listening on IPv4 address "0.0.0.0", port 5432
5efd9ee0a7da 2026-10-24 14:43:24.026 UTC [1] LOG: could not create IPv6 socket for address "::": Address family not supported by protocol
5efd9ee0a7da 2026-10-24 14:43:24.028 UTC [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
5efd9ee0a7da 2026-10-24 14:43:24.030 UTC [78] LOG: database system was shut down at 2026-10-24 14:43:23 UTC
5efd9ee0a7da 2026-10-24 14:43:24.033 UTC [1] LOG: database system is ready to accept connections
5efd9ee0a7da 2026-10-24 14:43:35.884 UTC [85] ERROR: relation "translation_overrides" does not exist at character 523
5efd9ee0a7da 2026-10-24 14:43:35.884 UTC [85] STATEMENT: SELECT a.attname, format_type(a.atttypid, a.atttypmod),
5efd9ee0a7da pg_get_expr(d.adbin, d.adrelid), a.attnotnull, a.atttypid, a.atttypmod,
5efd9ee0a7da c.collname, col_description(a.attrelid, a.attnum) AS comment,
5efd9ee0a7da attidentity AS identity,
5efd9ee0a7da attgenerated as attgenerated
5efd9ee0a7da FROM pg_attribute a
5efd9ee0a7da LEFT JOIN pg_attrdef d ON a.attrelid = d.adrelid AND a.attnum = d.adnum
5efd9ee0a7da LEFT JOIN pg_type t ON a.atttypid = t.oid
5efd9ee0a7da LEFT JOIN pg_collation c ON a.attcollation = c.oid AND a.attcollation <> t.typcollation
5efd9ee0a7da WHERE a.attrelid = '"translation_overrides"'::regclass
5efd9ee0a7da AND a.attnum > 0 AND NOT a.attisdropped
5efd9ee0a7da ORDER BY a.attnum
5efd9ee0a7da
8d5cebf1355b run-parts: executing /etc/runit/1.d/00-ensure-links
8d5cebf1355b run-parts: executing /etc/runit/1.d/00-fix-var-logs
8d5cebf1355b run-parts: executing /etc/runit/1.d/01-cleanup-web-pids
8d5cebf1355b run-parts: executing /etc/runit/1.d/anacron
8d5cebf1355b run-parts: executing /etc/runit/1.d/cleanup-pids
8d5cebf1355b Cleaning stale PID files
8d5cebf1355b run-parts: executing /etc/runit/1.d/copy-env
8d5cebf1355b run-parts: executing /etc/runit/1.d/install-ssl
8d5cebf1355b Skipping ssl setup: missing /shared/ssl/ssl.crt or /shared/ssl/ssl.key
8d5cebf1355b Started runsvdir, PID is 45
8d5cebf1355b nginx: [emerg] socket() [::]:80 failed (97: Address family not supported by protocol)
8d5cebf1355b nginx: [emerg] socket() [::]:80 failed (97: Address family not supported by protocol)
8d5cebf1355b nginx: [emerg] socket() [::]:80 failed (97: Address family not supported by protocol)
8d5cebf1355b nginx: [emerg] socket() [::]:80 failed (97: Address family not supported by protocol)
8d5cebf1355b nginx: [emerg] socket() [::]:80 failed (97: Address family not supported by protocol)
8d5cebf1355b nginx: [emerg] socket() [::]:80 failed (97: Address family not supported by protocol)
Disabling IPv6 support on the host machine breaks Discourse deployment with the recipe. It would be great if you could recommend a fix here.