Workers execute ticket sessions for projects. Each worker is created from a provider, runs in Docker, and accepts work according to its policy and the projects that are allowed to use it.
Prepare worker execution
Workers require Docker and the managed worker image. Open Settings → Workers to build or rebuild the image and view progress and logs in the dashboard.
On Linux, configure worker confinement before creating your first worker:
On a new Linux installation with no workers, Readiness may be unable to determine the confinement state. Run this command before creating the first worker even if the screen cannot determine it.
Worker lifecycle
Workers expose lifecycle and health state through the dashboard. LStack monitors heartbeats, adopts durable worker resources after a core restart, and prevents unavailable workers from receiving new assignments.
Assignment eligibility
A worker can receive a ticket only when:
- The worker is healthy and available.
- The project is allowed to use it.
- Its provider and policy permit the assignment.
- It has not reached its active-session limit.
Isolation boundary
The dashboard runs on the host, while worker execution occurs in managed Docker containers. LStack mounts only the execution paths and resources required for assigned work.
Rebuilding the worker image does not update existing worker containers. Recreate workers to use the rebuilt image.
