I’ve a problem upgrading docker (discourse/discourse) from 2026.7.3 to 2026.7.4 (also the 2026.11.0-latest have the same problem): # terminated with exception (report_on_exception is true): /var/www/discourse/lib/discourse_vips/client.rb:50:in 'block in DiscourseVips::Client.call': libvips operation failed (DiscourseVips::Error) from /var/www/discourse/lib/image_processing/instrumentation.rb:6:in 'ImageProcessing::Instrumentation.instrument' from /var/www/discourse/lib/discourse_vips/client.rb:40:in 'DiscourseVips::Client.call' from /var/www/discourse/lib/discourse_vips.rb:14:in 'DiscourseVips.version' from /var/www/discourse/lib/letter_avatar.rb:140:in 'LetterAvatar.vips_version' from /var/www/discourse/lib/letter_avatar.rb:36:in 'LetterAvatar.version' from /var/www/discourse/lib/discourse.rb:1343:in 'block in Discourse.preload_rails!' /var/www/discourse/lib/discourse_vips/client.rb:50:in 'block in DiscourseVips::Client.call': libvips operation failed (DiscourseVips::Error) from /var/www/discourse/lib/image_processing/instrumentation.rb:6:in 'ImageProcessing::Instrumentation.instrument' from /var/www/discourse/lib/discourse_vips/client.rb:40:in 'DiscourseVips::Client.call' from /var/www/discourse/lib/discourse_vips.rb:14:in 'DiscourseVips.version' from /var/www/discourse/lib/letter_avatar.rb:140:in 'LetterAvatar.vips_version' from /var/www/discourse/lib/letter_avatar.rb:36:in 'LetterAvatar.version' from /var/www/discourse/lib/discourse.rb:1343:in 'block in Discourse.preload_rails!' E, [2026-11-09T11:44:20.275076 #11010] ERROR -- : mold gen=0 pid=11013 reaped (# ) I, [2026-11-09T11:44:20.275357 #11010] INFO -- : reaped unknown subprocess # /var/www/discourse/vendor/bundle/ruby/4.0.0/gems/pitchfork-0.18.2/lib/pitchfork/http_server.rb:179:in 'Pitchfork::HttpServer#start': The initial mold failed to boot (Pitchfork::BootFailure) from /var/www/discourse/vendor/bundle/ruby/4.0.0/gems/pitchfork-0.18.2/exe/pitchfork:110:in ' ' from /usr/local/lib/ruby/4.0.0/rubygems.rb:305:in 'Kernel#load' from /usr/local/lib/ruby/4.0.0/rubygems.rb:305:in 'Gem.activate_and_load_bin_path' from /var/www/discourse/vendor/bundle/ruby/4.0.0/bin/pitchfork:25:in ' ' ./config/unicorn_launcher: line 93: kill: (11010) - No such process ./config/unicorn_launcher: line 13: kill: (11010) - No such process (10949) exiting Can you please check the builds?

Are you using a standard install?

Hello David, I’m using version discourse/discourse on docker hub (discourse/discourse - Docker Image) with “redis:7-alpine” and “discourse/postgres:latest”. Here my current configuration (as docker compose): services: redis: image: redis:7-alpine container_name: redis volumes: - /volume1/docker/discourse/redis_data:/data:rw ports: - '6379:6379' command: "redis-server --appendonly yes" restart: unless-stopped labels: - 'wud.tag.include=^([0-9]\d*)\-alpine$$' - 'wud.watch.digest=true' - 'wud.display.name=DiscourseRedis' - 'wud.display.icon=mdi:map-search' discourse_db: image: discourse/postgres:latest container_name: discourse_db volumes: - /volume1/docker/discourse/discourse_postgres:/var/lib/postgresql:rw - /volume1/docker/discourse/discourse_postgres_data:/var/lib/postgresql/data:rw environment: POSTGRES_DB: discourse POSTGRES_USER: admin POSTGRES_PASSWORD: "***" DB_USER: discourse_user DB_PASSWORD: "***" restart: unless-stopped labels: - 'wud.watch.digest=true' - 'wud.display.name=DiscoursePostgres' - 'wud.display.icon=mdi:map-search' discourse: image: discourse/discourse:2026.7.3 container_name: discourse depends_on: - discourse_db - redis ports: - '8093:80' volumes: - /volume1/docker/discourse/discourse_data:/shared environment: DISCOURSE_HOSTNAME: my.host.name DISCOURSE_DEVELOPER_EMAILS: "my@email.eu" DISCOURSE_DB_HOST: discourse_db DISCOURSE_DB_PORT: 5432 DISCOURSE_DB_NAME: discourse DISCOURSE_DB_USERNAME: discourse_user DISCOURSE_DB_PASSWORD: "***" DISCOURSE_REDIS_HOST: redis DISCOURSE_REDIS_PORT: 6379 DISCOURSE_SMTP_ADDRESS: 10.10.x.x DISCOURSE_SMTP_PORT: 587 DISCOURSE_SMTP_ENABLE_START_TLS: true DISCOURSE_SMTP_USER_NAME: my DISCOURSE_SMTP_PASSWORD: "****" #DISCOURSE_SMTP_FORCE_TLS: true DISCOURSE_SMTP_DOMAIN: my.domain DISCOURSE_SMTP_AUTHENTICATION: login DISCOURSE_SMTP_OPENSSL_VERIFY_MODE: none DISCOURSE_NOTIFICATION_EMAIL: noreply@email.eu LANG: it_IT.UTF-8 restart: unless-stopped labels: - 'wud.tag.include=^([0-9]\d*)\.([0-9]\d*)\.([0-9]\d*)$$' - 'wud.watch.digest=true' - 'wud.display.name=Discourse' - 'wud.display.icon=mdi:map-search'

The discourse/discourse image is still experimental, and isn’t something that we regularly test. That said, I have mentioned it internally so we’ll see if someone can take a look. For a production installation, we recommend the standard install procedure.

[image] pfaffman: Discourse won’t run on a non standard port and requires https. It won’t work on port 8093 Sorry, but it always worked as it’s simply the port mapping of the docker container. Also the SSL encapsulation is provided by NGINX, and shouldn’t be a problem for discourse. The error I receive with releases from end of October, is due to libvips changes as image processor, not socket-related :thinking:

Just tried the newly released 2026.7.5, but errors with libvips are still there: # terminated with exception (report_on_exception is true): /var/www/discourse/lib/discourse_vips/client.rb:50:in 'block in DiscourseVips::Client.call': libvips operation failed: Landlock child setup failed: Landlock::SyscallError: seccomp(SECCOMP_SET_MODE_FILTER) failed: Invalid argument (DiscourseVips::Error) from /var/www/discourse/lib/image_processing/instrumentation.rb:6:in 'ImageProcessing::Instrumentation.instrument' from /var/www/discourse/lib/discourse_vips/client.rb:40:in 'DiscourseVips::Client.call' from /var/www/discourse/lib/discourse_vips.rb:14:in 'DiscourseVips.version' from /var/www/discourse/lib/letter_avatar.rb:140:in 'LetterAvatar.vips_version' from /var/www/discourse/lib/letter_avatar.rb:36:in 'LetterAvatar.version' from /var/www/discourse/lib/discourse.rb:1310:in 'block in Discourse.preload_rails!' /var/www/discourse/lib/discourse_vips/client.rb:50:in 'block in DiscourseVips::Client.call': libvips operation failed: Landlock child setup failed: Landlock::SyscallError: seccomp(SECCOMP_SET_MODE_FILTER) failed: Invalid argument (DiscourseVips::Error) from /var/www/discourse/lib/image_processing/instrumentation.rb:6:in 'ImageProcessing::Instrumentation.instrument' from /var/www/discourse/lib/discourse_vips/client.rb:40:in 'DiscourseVips::Client.call' from /var/www/discourse/lib/discourse_vips.rb:14:in 'DiscourseVips.version' from /var/www/discourse/lib/letter_avatar.rb:140:in 'LetterAvatar.vips_version' from /var/www/discourse/lib/letter_avatar.rb:36:in 'LetterAvatar.version' from /var/www/discourse/lib/discourse.rb:1310:in 'block in Discourse.preload_rails!' E, [2026-11-11T09:08:04.096537 #1021] ERROR -- : mold gen=0 pid=1024 reaped (# ) I, [2026-11-11T09:08:04.096668 #1021] INFO -- : reaped unknown subprocess # /var/www/discourse/vendor/bundle/ruby/4.0.0/gems/pitchfork-0.18.2/lib/pitchfork/http_server.rb:179:in 'Pitchfork::HttpServer#start': The initial mold failed to boot (Pitchfork::BootFailure) from /var/www/discourse/vendor/bundle/ruby/4.0.0/gems/pitchfork-0.18.2/exe/pitchfork:110:in ' ' from /usr/local/lib/ruby/4.0.0/rubygems.rb:305:in 'Kernel#load' from /usr/local/lib/ruby/4.0.0/rubygems.rb:305:in 'Gem.activate_and_load_bin_path' from /var/www/discourse/vendor/bundle/ruby/4.0.0/bin/pitchfork:25:in ' ' ./config/unicorn_launcher: line 93: kill: (1021) - No such process ./config/unicorn_launcher: line 13: kill: (1021) - No such process (949) exiting

Landlock::SyscallError: seccomp(SECCOMP_SET_MODE_FILTER) failed: Invalid argument (DiscourseVips::Error) What kind of machine are you running Discourse on? Does it have an up-to-date linux Kernel? Any unusual virtualization going on?

[image] david: What kind of machine are you running Discourse on? Does it have an up-to-date linux Kernel? Any unusual virtualization going on? It’s a Synology NAS, with fw DSM 7.4.1-90080 Update 1 (latest available), which runs on an old kernel version (4.4.302) as any Synology NAS. Could this be the problem?

The old kernel version means you wouldn’t be able to run the ‘Landlock’ sandboxing. But that should degrade gracefully, and show a large warning in the admin panel. The problem here seems to be the ‘seccomp’ protections, which we try to apply in all situations. If the synology kernel is missing seccomp (which sounds likely), then that explains the failure. We might be able to make it fail more gracefully, but then your forum’s image processing would be running with absolutely no sandboxing. So either way, I’d strongly recommend trying to find a more up-to-date/secure environment to run your forum, especially if it’s on the public internet. Image processing is becoming an increasingly common vector for exploits in recent months, which is why we’ve added the sandboxing.

Thank you for clarification, I’ll change the host of the forum, moving it on a minipc with Proxmox. Thanks!

Libvips upgrade error

Product Support Self-hosting

pfaffman (Jay Pfaffman) November 11, 2026, 5:13am 6

Discourse won’t run on a non standard port and requires https. It won’t work on port 8093

Topic		Replies	Views
Determining whether my VPS needs any upgrades (generally) Product Support	20	1080	March 10, 2025
Docker version not supported after the later update Self-hosting	2	1273	November 4, 2017
Upgrading old version 2.8.5 issues Self-hosting	26	719	December 15, 2025
ERROR: You are running an old version of the Discourse image Self-hosting	11	1784	May 4, 2021
Update broken stuck on Docker version Product Support	9	577	February 14, 2025

Libvips upgrade error

Related topics