IO Worker - Automatically Deleting Docker Containers

This guide covers what to do when containers are removed / deleted when starting the IO Worker.

1️⃣ Isolated containers

• For security reasons, IO containers must operate independently. They cannot run alongside other containers / docker projects. 
• When your worker is connected to io.net, the resources of the device should be fully dedicated to the platform. If the device's computational capacity is limited or used for other purposes, it may result in disqualification from rewards and hiring. Resources must remain fully available while your device is active on io.net.

2️⃣ GPU/CPU Monitoring

• IO monitors GPU/CPU usage to ensure participants are not overloading the system or exploiting it for rewards. If GPU/CPU usage consistently hits or exceeds a specific threshold, this may be considered abuse. In such cases, the worker may be blocked to maintain fairness and stability.
• Running other applications on the device can overload the GPU/CPU, leading to the device being blocked from the network.
  

Additional Information:
Device Utilization - Discord Announcement
Device Utilization Threshold
What is Proof of Work (POW)?