Builds are stopped
Weik.io 2026.2A hub server's kernel can't limit a build step's network connections, so no version builds on it until a platform administrator allows builds or you move the hub to a supported server.
| Kind | Severity | Who sees it |
|---|---|---|
builds- |
Warning | Platform administrators, in a list that isn’t narrowed to an environment or a project |
What it means#
No version builds on the hub server the problem is about, so an apply that would build a version there fails. To allow builds, run the command at the end of the apply’s error. Versions that are already built still deploy and run.
What raises it#
The hub server’s kernel is older than Linux 6.7, or Landlock is off on it, so a build step’s network connections can’t be limited. The installation’s settings don’t allow builds without that limit. The detail has the server and the command that allows builds.
What to check#
Run doctor in the stack’s folder on the hub server. The build isolation line of its builder section says what the kernel can’t limit for a build step, and why:
$ docker compose run --rm infra weikio-backend doctorSee whether the installation allows builds without the limit. The allowBuildsWithoutNetworkLimit line shows false when it doesn’t:
$ weikio settings getHow to fix it#
Move the hub to a server with Linux 6.7 or later and Landlock enabled, such as Ubuntu 24.04. To build on the server you have, allow builds without the limit:
$ weikio settings set --allow-builds-without-network-limit=trueIn the admin UI, set Builds without a network limit to Allowed in Edit installation settings on Settings › Installation. A build step on that server then runs with the limits its kernel has. Its TCP connections aren’t limited, so it can reach the hub’s own service ports. The problem clears once builds are allowed, but doctor still warns about the kernel.