Network volumes temporarily disabled for CPU Pods - timeline query
Hi folks,
We noticed that network volumes are temporarily disabled for CPU pods, which is blocking our scholars’ weekend experiments. Can you share an estimated timeline for restoration? Thanks!
Iftekhar (MATS)
5 Replies
We are targeting to enable it around mid/late February
Thanks for the timeline. In the meantime, we're facing these issues:
1. We need CPU pods, as GPU pods don't appear to support Docker containers.
2. If we deployed CPU pods without network volumes, the instance would crash after building ~3 samples due to running out of disk space.
Are there any workarounds/alternatives you'd recommend while we wait for restoration? Thanks for your help!
use digitalocean maybe, to build your docker images or aws ec2
our transition we are doing to cpu pods will not support running docker in containers, we used kata-containers for current cpu pods and its causing issues with data loss in network volumes, we are transitioning away from it and using normal containers
we are experimenting with sysbox to allow vm like functionality in containers, that will come to cpu pods first, no eta for that yet
Thank you folks for the info and the suggestions.