Skip to content

feat(server)!: configure the server with server.toml and run workers on Podman - #1470

Merged
kvlonge merged 5 commits into
mainfrom
feat/server-config
Nov 14, 2026
Merged

kvlonge merged 5 commits into
mainfrom
feat/server-config

Conversation

@kvlonge

@kvlonge kvlonge commented Nov 14, 2026

Copy link
Copy Markdown
Contributor

Why

Running the server in containers, and on Podman in particular, meant several config files, a pile of flags, and workers that ignored container limits. Container health checks also needed a way to tell when a code location was down or falling back to an older load.

Changes

  • sqb server and sqb scheduler --config server.toml read [server], [retention], [oidc], [trusted_proxy] and [launchers.*] from one file, and a flag overrides the file. Launchers name their location, which is resolved when the server starts. BREAKING CHANGE: --launchers, --oidc-config and --trusted-proxy-config are replaced by --config.
  • Docker workers take limits from a job's resources(memory, cpus, pids), then the launcher's [launchers.docker.run] table, then the location container. max_memory caps them; without it, a job can't go above the location container's limits. Workers keep the location's dropped capabilities and security options.
  • sqb location health prints a target's state and exits 1 when the location is down or falling back, for use in container health checks. GET /api/locations/{id}/health takes an optional target.
  • Workers join the location's named network on Podman. The Dockerfile can install a released version. A new Verify job runs the packaged Compose lifecycle on Podman.
  • Docs: server.toml, worker limits, Podman and the new sqb dev and sqb location pages. DuckShop gains a container resources edge case.

Verification

  • make check-ci passed on the final head.
  • Native command tests passed 15/15, including a sqb location health case that fails without the per-target read. Orchestration native tests passed 133/133.
  • On rootful Podman, the login, recovery and worker suites passed (48), the Docker worker suite passed after the review fixes (10), and the packaged Compose lifecycle passed (2).
  • A real podman compose stack ran a worker.
  • The new Podman CI job is unproven on GitHub's runners until this PR's run.

Launchers name their location and are resolved once at start-up.

BREAKING CHANGE: --launchers, --oidc-config and --trusted-proxy-config are replaced by
sqb server --config server.toml with [[launchers.docker]], [[launchers.local]], [oidc] and
[trusted_proxy] sections. The old flags fail with a pointer to --config.
…ob resources

Docker workers keep the location container's dropped capabilities and security options,
take [launchers.docker.run] memory, cpus, pids and cgroup_parent, and a job's resources,
with max_memory as the ceiling. Only positive limits are sent, so Podman workers are not
started with a zero process limit. The reference image can install a released SQLBuild.
sqb location health prints a target's state and exits 1 when no instance has checked in for
90 seconds or its last load failed. Docker workers join the location's named network when
Podman reports it as bridge. A path-filtered and nightly Verify job runs the packaged Compose
lifecycle on rootful Podman. sqb dev and sqb location get documentation pages.
@kvlonge kvlonge added the full-verify Run the full Verify matrix on this pull request label Nov 14, 2026
@kvlonge
kvlonge enabled auto-merge November 14, 2026 03:46
… job

GitHub's Ubuntu runner keeps /run/podman private to root, so changing the
socket's group alone left the runner user unable to connect.
Podman has no BuildKit API, so buildx on the runner built in its own BuildKit
container and the images never reached Podman's store.
@kvlonge
kvlonge added this pull request to the merge queue Nov 14, 2026
Merged via the queue into main with commit 88cbbd1 Nov 14, 2026
45 checks passed
@kvlonge
kvlonge deleted the feat/server-config branch November 14, 2026 06:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

full-verify Run the full Verify matrix on this pull request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant