IO Worker Automatically Deleting Other Docker Containers

When starting the IO worker, it deletes my other containers. 

1️⃣ For security reasons IO containers must work alone, they cannot work with other containers. 

• While your worker is connected to io.net, its resources should be fully dedicated to the platform. If the device’s computational capacity is limited or used elsewhere, it may result in disqualification from rewards and hiring. 
• we expect resources to be fully available while your device is made available on io.net.

2️⃣ IO monitors GPU/CPU utilization

• IO monitors GPU/CPU utilization to ensure that participants are not overloading the system or exploiting it for rewards. If the GPU/CPU usage consistently hits or exceeds a set threshold, it may be considered abuse, causing the worker to be blocked to maintain fairness and stability. 
• Running any other application in your devices can overload GPU/CPU and result device getting blocked from the network 

---

2️⃣ helpful links to increase your knowledge on how this process works.

• Device Utilization - Discord Announcement
• Device Utilization Threshold
• What is Proof of Work (POW)?