English
Semaphore Runner Hosting
Semaphore Runner is the separate job agent that registers with Semaphore UI and executes assigned playbooks away from the web console.
- One click deploy
- 15 GB Disk Space Needed
- 1 GB RAM Memory needed
- From 2 € Price
No setup fees
Official links
Semaphore Runner’s official links and original website
- Go to Repository
Semaphore Runner GitHub
- More
Semaphore Runner Website
What you get
on AvaHost
One-click deployment, a custom domain, free HTTPS, automatic application updates, and scheduled backups come with every Cloud App. You can run multiple apps on one server, and terminal access is included.
This template does not include a database container.
Tech
- Docker image
- semaphoreui/runner:latest
- Default port
- 0
How Semaphore Runner works
Semaphore Runner is not a second copy of the website. The semaphoreui docs describe a process you start on another server. It connects to Semaphore UI, marks itself ready, receives a task, clones the repository the task names, and runs Ansible, Terraform, PowerShell, or a similar job. Results go back to the server. The Docker image is semaphoreui/runner. Registration uses a token from the server, either created in the UI or with the runner register command when the server has a registration token configured.
There is no database inside the runner. It stores its token in a file under the data or temp path the wrapper documents. It needs a URL it can open to your Semaphore UI, over HTTPS in any setup you would actually trust. Extra Python dependencies can be installed at start from a requirements file mounted into the config directory, the same pattern as the server image.
Key Semaphore Runner features
One Semaphore server can have several runners, and tasks spread across the ones that are free. That is how you keep a playbook inside a closed network while the UI sits on the public hostname. The runner can be limited in how many tasks it accepts at once. Those knobs are in the runner config, not in a marketing page. The icon shipped for this app matches the Semaphore UI icon file byte for byte, because the project shares one mark. The two deployments are still different containers.
AvaHost updates the runner container automatically and can back up the small token file on a schedule. It cannot back up the inventories stored in Semaphore UI, and it does not know the contents of the private networks you point jobs at. Application mail is not included with Semaphore Runner.
Self-hosting Semaphore Runner: requirements and cost
The baseline is 1024 MB of RAM and 1 CPU core, image semaphoreui/runner, no database. Playbooks that compile or copy large artifacts can want more disk on the runner than the UI needs. On AvaHost the recommended minimum for Semaphore Runner is Plan 1 at €2. The package includes one-click deployment, automatic updates, and scheduled backups of the runner's own files. It does not include a public website, a dedicated IP, or the Semaphore server. Point it at the Semaphore URL you already operate.
Who uses Semaphore Runner
Use this package only beside a Semaphore UI you can already sign in to. Typical users are teams who refuse to let the web server touch production networks, or who want a second execution host when one runner is busy. If you have no Semaphore server, this container has nowhere to register and no page to show a visitor. Order Semaphore UI first, or skip this app.
F.A.Q
Semaphore Runner starts at €2 on Plan 1. You are paying for the agent container and its token file, not for Semaphore UI and not for the machines the playbooks change. Heavy compile jobs or large checkouts can need more RAM or disk than this minimum. The Semaphore server, if it is also on AvaHost, is its own app and its own plan.
No. There is no visitor UI on this package. The process opens an outbound connection to the Semaphore server URL you configure and waits for tasks. Put the hostname and the certificate on Semaphore UI. The runner only needs to reach that URL and to keep its registration token.
AvaHost updates the runner automatically and backs up its local files, including the token file, on a schedule. The projects, inventories, and task history live on the Semaphore server, so back those up there. After an update, confirm the runner still shows as ready and complete one harmless task before production work.
No. Upstream registration requires a Semaphore server address and a token. This catalog lists the runner separately so you can place execution on another VPS, not so it can replace the console. If the server is down or the token is wrong, the container has no work to do and no page to explain that.