Currently, fn dind likely grabs the same disk/location for its /var/lib/docker as the parent docker, where both dockers end up using the same disk space. To track this, some notes below:
- dedicated parent docker /var/lib/docker volume/storage.
- dedicated dind docker /var/lib/docker volume/storage for fn pods. And this needs to be cleaned up before starting up (and after tearing down) fn pod.
- strategy to handle how to handle the full capacity cases in both. (most likely a clean & restart)