Failing a marketplace check
The readiness check documents every requirement. This page is the shortlist: the ones that actually stop people, in the order worth fixing them.
Fix these first — they block everything
Section titled “Fix these first — they block everything”No public IPv4. Behind carrier NAT the machine can be listed and never rented. Nothing else you fix matters until this does. Ask your ISP for a dedicated address, or put the machine behind a VPS with a tunnel.
Docker not running, or no NVIDIA Container Toolkit. A rental is a container. Without the toolkit the container starts and sees no GPU — the tenant pays for a card that is not there, which is the worst possible failure because everything looks healthy from outside.
Two marketplace agents on one machine. See one machine, one marketplace. Some agents remove containers they did not create, so this is not a tidiness issue.
The Vast disk-quota pair
Section titled “The Vast disk-quota pair”Two rows that look similar and are not.
Docker filesystem — needs XFS with pquota. Vast enforces per-tenant disk
quotas, and quotas are an XFS feature. On ext4 the host is refused.
Disk quota enforced — needs the classic overlay2 driver. This is the
one that catches people who already did the first. With the containerd
snapshotter enabled, Docker accepts --storage-opt size and silently
ignores it: a container told to fit in 10 GB sees the whole disk. Nothing
errors until a tenant fills your drive.
Fix: remove features.containerd-snapshotter from /etc/docker/daemon.json,
restart Docker. Images pulled under the other snapshotter become invisible —
export what you need first.
Verdicts that are not really failures
Section titled “Verdicts that are not really failures”Unknown. Not measured, or nothing can measure it. Run the check again first; a handful of rows need you to confirm the fact yourself because no probe can.
Warn. Met, but below the recommendation. It does not block the listing. Worth fixing when it affects price — bandwidth and RAM both do — and worth ignoring otherwise.
Overclock and power limit — stock. Clore requires factory clocks. If you set a power limit yourself, this row will warn. Lower limits save electricity and heat; on Clore they can cost you price tier. Your call, per machine.
The one that comes back after a reboot
Section titled “The one that comes back after a reboot”Kernel against driver, on Clore. Kernel 6.16 and newer will not build driver branches R550 and older. The pair fails at boot, so the machine comes back without a GPU rather than failing at rental time.
Fix either side — move the driver to R590, or pin an older kernel. It is the combination that breaks, not either one alone.
After fixing anything
Section titled “After fixing anything”Re-run the check. A row changes when the machine is measured again, not when you say you changed it.