# Libvips upgrade error

**URL:** <https://meta.discourse.org/t/libvips-upgrade-error/416912>\
**Category:** Self-hosting\
**Tags:** unsupported-install\
**Created:** [November 9, 2026, 12:15pm UTC](https://meta.discourse.org/t/libvips-upgrade-error/416912 "2026-11-09T12:15:13Z")\
**Posts on this page:** 1\
**Showing post:** 11

<div class="post-metadata">

**Author:** ![david](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/david/32/157490_2.png) [@david](https://meta.discourse.org/u/david)\
**Post date:** [November 11, 2026, 11:54am UTC](https://meta.discourse.org/t/libvips-upgrade-error/416912/11 "2026-11-11T11:54:13Z")

</div>

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](https://github.com/nextcloud/all-in-one/discussions/5768)), 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.

---

_[View the full topic](https://meta.discourse.org/t/libvips-upgrade-error/416912)._
