Default Jobs

Default Jobs are reusable fallback workload profiles for provider nodes. Assign a profile to a node, and Lium can run that workload while the node is idle and unrented.

Runtime priority

Default Jobs are best-effort idle workloads. Customer rentals always have priority, and a running Default Job can be stopped when the node is needed for a rental or when the assignment is disabled, cleared, changed, or deleted.

What Default Jobs are

Use Default Jobs to:

• Save a reusable workload profile in the Provider Portal.
• Assign that profile to one or more owned nodes.
• Bulk-assign a profile across a larger fleet.
• Leave a node in the No Default Job state when you do not want an idle workload on it.

Default Jobs do not create customer rental records, billing records, or customer pods.

Default Jobs and the unrented incentive

On an idle node, running your own Default Job and earning the unrented incentive are mutually exclusive. Per node you choose one:

• Run your own Default Job (Pearl Mining or Custom Docker) — you keep everything that job earns, but the node earns no unrented incentive while your own Default Job is assigned.
• No Default Job — the node keeps its unrented incentive, and Lium runs its own Default Job on the idle node so it still does useful work.

This trade-off applies only while the node is idle. When a customer rents the node, it earns rental income and the rented-pool share exactly as before, regardless of any Default Job assignment.

Before you start

Before creating a Default Job, make sure:

1. You are signed in to the Provider Portal with your provider hotkey.
2. Your provider is connected, either self-hosted or through the Lium.io Central Provider Server.
3. You have at least one registered node. See Managing Nodes.
4. For Pearl Mining, you have your Akoya pool wallet and worker values.
5. For Custom Docker, you have a public image and a command that keeps the container running.

Create a Pearl Mining profile

Pearl Mining is a locked preset. You only provide a profile name and the required pool environment values; the image, tag, storage, volume, and port are set by the template.

1. Open Default Jobs in the Provider Portal.
2. Click Create Job.
3. Select Pearl Mining.
4. Enter a Job Name.
5. Add the required environment variables:
   • AKOYA_POOL_WALLET
   • AKOYA_POOL_WORKER
6. Click Save Default Job.

The Pearl Mining preset uses:

Field	Value
Image	registry.akoyapool.com/akoya-miner:1.0.2
Storage limit	20 GB
Volume	/root
Internal port	22

Create a Custom Docker profile

Use Custom Docker when you want to run your own long-running container on idle nodes.

1. Open Default Jobs in the Provider Portal.
2. Click Create Job.
3. Select Custom Docker.
4. Fill the required fields:
   • Job Name: a readable name for the profile.
   • Image and Image Tag: for example, alpine and 3.20.
   • Command / Args: a command that keeps the container alive, such as sleep infinity.
   • Disk Limit GB: required, from 1 to 100 GB.
5. Add optional fields if your image needs them:
   • Environment Variables as KEY=value lines.
   • Volumes as comma-separated mount paths.
   • Internal Ports as comma-separated container ports.
   • Minimum VRAM MB and Minimum GPU Count for node-fit requirements.
6. Click Save Default Job.

Keep the process running

If the Custom Docker command exits, the Default Job run ends. Use a long-running worker process, service command, or an explicit command such as sleep infinity for smoke testing.

Assign profiles to nodes

After saving a profile, assign it in the Node Assignment table.

Assign one node

1. Find the node row.
2. Open the Default Job dropdown.
3. Select the profile.

Assign multiple nodes

1. Select the checkboxes for the target nodes.
2. Choose a profile from the bulk assignment dropdown.
3. Click Apply to selected.

To remove an assignment, choose No Default Job. Each node can have only one active Default Job assignment.

Monitor runs and activity

The Default Jobs page shows runtime signals in two places:

• Node Assignment: current assignment state, runtime status, last event time, runtime today, and failure reason when available.
• Node Activity: recent customer rentals and Default Job runs across your owned nodes.

Assignment statuses include No Default Job, Assigned, and Disabled. Runtime statuses can include Idle, Starting, Running, Stopping, Failed, or Blocked.

Disable, clear, or delete

Use the smallest action that matches what you want:

Action	Where	Result
Disable a profile	Edit the Default Job and turn the Enabled switch off	The profile is kept, but the runtime will not start it. Existing assignments remain visible.
Clear an assignment	Set a node to No Default Job	The node no longer has an active fallback workload assignment.
Delete a profile	Open the profile details and click Delete	The profile is removed and its active assignments are cleared.

When a running Default Job becomes inactive because the profile or assignment changed, the runtime stops it on a later runner cycle.

Limits and behavior

• Default Jobs run only on active, idle nodes with an enabled profile assignment.
• Running your own Default Job forfeits the node's unrented incentive while it is assigned; leaving a node in No Default Job keeps the incentive. See Default Jobs and the unrented incentive.
• Customer rentals have priority over Default Jobs.
• A node can have only one active Default Job assignment.
• Custom Docker disk limits must be between 1 and 100 GB.
• The runtime checks node fit before launch, including free GPUs, optional minimum GPU count, optional minimum VRAM, disk space, and required internal ports.
• Runs are best-effort and can be skipped or stopped by runtime conditions.