TroubleshootingNot Earning
Not getting container jobs
A checklist to make your machine container-ready when it only ever gets bandwidth or mining jobs, or no container jobs at all.
Container jobs are the best-paying work on Salad, and the network only offers them to machines that pass every check below. Work through the list; most Chefs who "never get containers" are missing one item.
- An in-demand, dedicated GPU. Check your card on the Network Monitor. Integrated graphics don't qualify, and only one GPU per PC can earn (multi-GPU).
- GPU and CPU both enabled under Settings > Configure Hardware (how).
- 16 GB or more system RAM (32GB+ recommended). Salad gives the container environment a share of it; less than that rules out most jobs.
- At least 70 GB free on the C: drive, more for larger jobs. Salad can't use other drives (why).
- Virtualization enabled in the BIOS (how to check and enable it) and no conflicting virtualization software (Android emulators).
- The container environment installed and healthy. Any Degraded notification blocks container jobs: Degraded State.
- The latest version of Salad (how to update).
- A stable connection with no VPN or proxy. Salad's startup speed test is used when assigning jobs, so run it on a healthy line; wired beats Wi-Fi (tips).
- The GPU at stock settings - no power limit, undervolt or thermal throttling (GPU power limit).
- Nothing else using the GPU, and the PC left alone. Salad is designed to run while you're away (close games and other programs).
- The first compatibility check completed. After a fresh install the machine has to finish one short check before paid jobs are offered; leave Salad running for at least 30 minutes.
If every item is in place and demand for your card is high, see Finding Job for hours.
Edit on GitHub
Last updated on
Why am I not receiving any jobs?
The two reasons a machine gets no jobs - low demand for its hardware, or a configuration that stops it qualifying - and how to check each.
My earning rate has dropped to 0
Why the earning rate shows 0 between jobs, when that's normal, and what to check when it never comes back.

