Readiness check failures
Start with the name and result of the failing row on the Platforms tab. The full description is in the readiness check.
Check the network and containers first
Section titled “Check the network and containers first”Public IPv4 and ports. Check access from outside the network. With CGNAT, regular port forwarding on your router is not enough; ask your provider about a public address.
Docker and NVIDIA Container Toolkit. Docker must be running, and containers must have access to the GPUs. Installing the Flotera agent does not replace configuring the rental environment.
Marketplace agent conflict. If the check reports a conflict, inspect the marketplace services on the server and follow each marketplace’s host setup instructions. Flotera does not install or remove these agents.
Vast disk quotas
Section titled “Vast disk quotas”Check separately:
- XFS and the
pquotaproject quota option for the Docker data directory; - the actual enforcement of the container size limit.
If the first check passes and the second does not, check the storage driver
in use with docker info. For a quota configuration with overlay2,
the containerd storage may require explicit disabling depending on the
Docker version. Simply removing the parameter from daemon.json does not
guarantee a mode switch.
Unknown and Warn
Section titled “Unknown and Warn”Unknown: insufficient data. Rerun the check and check its source. Some rows require manual confirmation.
Warn: a deviation from the recommendation. Read the explanation: it may indicate a performance or compatibility limitation, even if it does not block publication.
GPU settings on Clore
Section titled “GPU settings on Clore”Check the allowed model, the driver branch, and the factory GPU settings. A power limit set in Flotera can trigger a warning. Match the setting with the marketplace requirements before qualification.
GPUs disappeared after a reboot
Section titled “GPUs disappeared after a reboot”Check the compatibility of the installed kernel and NVIDIA driver, as well as the result of the driver module build. Choose a compatible version pair based on the current requirements. Reinstalling the agent does not restore the GPU driver.
After fixing
Section titled “After fixing”Rerun the check. If the result has not changed, save the row name, the expected and actual values, the agent version, and the error text.