Spare Cores Runner
Spare Cores Runner is a command-line tool and Python API designed to simplify the process of provisioning and managing cloud instances across various cloud providers. It leverages Pulumi to handle infrastructure-as-code and automate the creation and destruction of compute instances in your preferred cloud environment.
Spare Cores Runner (sc-runner from now on) is used by Spare Cores Inspector
to start up basic cloud instances with the required minimum configuration and environment to start the machine with a custom
cloud-init script, but it can also be used to simply start an instance with a given SSH key, making it available for basic
use cases.
Supported Cloud Providers and their Credentials
sc-runner uses the Spare Cores database to pre-fill the available configuration options, like what regions and instance
types are available for a given cloud provider.
To use a given cloud provider, you have to provide credentials for them, either by running it in an environment
where the underlying library can pick them up, or by specifying them through environment variables or command line options.
For more details, see the supported vendor's Pulumi integration:
Pulumi
As sc-runner uses Pulumi under the hood to manage the cloud providers, it'll need to have a Pulumi project.
You can configure Pulumi project-related settings either by specifying them using command line arguments, shown below:
sc-runner create --help
Usage: sc-runner create [OPTIONS] COMMAND [ARGS]...
Options:
--project-name TEXT Pulumi project name [default: runner]
--work-dir TEXT Pulumi work dir [default: /data/workdir]
--pulumi-home TEXT Pulumi home [default: /root/.pulumi]
--pulumi-backend-url TEXT Pulumi backend URL [default: file:///data/backend]
--stack-name TEXT Pulumi stack name, defaults to
{vendor}.{region}.{zone}.{instance_id} or similar
--help Show this message and exit.
Commands:
aws
azure
gcp
hcloud
alicloud
ovh
upcloud
vultr
Or by setting the following environment variables:
- PULUMI_PROJECT_NAME
- PULUMI_WORK_DIR
- PULUMI_HOME
- PULUMI_BACKEND_URL
sc-runner should create the project on the first invocation, during which it'll create multiple stacks for each
vendor.region.zone.instance_id tuple. This allows concurrent creation of instances, supporting our
Spare Cores Inspector use case, where we start a given instance type once to collect data from them.
Usage
CLI examples
Create instances
Create and destroy a default t3.micro instance in the default VPC/subnet in AWS:
sc-runner create aws
sc-runner destroy aws
Create an Azure instance with a public key:
sc-runner create azure --instance Standard_DS1_v2 --public-key $(cat .ssh/id_ed25519.pub)
Create an AWS instance with public IP and an already stored SSH key named spare_cores:
sc-runner create aws --region us-west-2 --instance t4g.large --instance-opts '{"associate_public_ip_address": true,"key_name":"spare-cores"}' --public-key ""
Destroy instances
sc-runner destroy azure --instance Standard_DS1_v2
sc-runner destroy aws --region us-west-2 --instance t4g.large
You can also use destroy-stack instead of destroy, which performs a pulumi refresh first, synchronizing the underlying
cloud state with Pulumi's internal backend and destroying only what's really there (so it won't fail on already deleted
resources).
Cancelling Pulumi Locks
Sometimes Pulumi might leave a lock file in its state store, preventing further operations. With this command you can cancel those:
sc-runner cancel aws --region us-west-2 --instance t4g.large
Docker
sc-runner is available through a Docker image as well, which you can use with the following command:
docker run --rm -ti ghcr.io/sparecores/sc-runner:main --help
You'll have to set up the same environment variables or configure the cloud credentials for Pulumi.
Metadata
Release files for sparecores-runner 0.0.81
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| sparecores_runner-0.0.81.tar.gz | 54.9 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| sparecores_runner-0.0.81-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 126.1 kB
Release files / sparecores_runner-0.0.81.tar.gz
| Download URL | sparecores_runner-0.0.81.tar.gz |
|---|---|
| Size | 54.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4a74042eb15fa3dff51a4edd157884c128ae3ad8e9bb83ee8f61fa314ba02d3b
|
|
BLAKE2b-256 checksum How to use checksums |
96cf7e57c5e0fb5e7e4d9875a96210a030960988f838ebd76455219310c27e23
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 11, 2026.
Transparency logRelease files / sparecores_runner-0.0.81-py3-none-any.whl
| Download URL | sparecores_runner-0.0.81-py3-none-any.whl |
|---|---|
| Size | 71.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ae5dd9481fbf009e22bb2215dc53a03c48ebe1e2904a6b9e0285e1c514c2a5ec
|
|
BLAKE2b-256 checksum How to use checksums |
ff3be824ccf49f420a1458110a38794d0bf15ddca6dcc734e77da58dbab49d3e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 11, 2026.
Transparency log
