Question-and-Answer Resource for the Building Energy Modeling Community
 | 1 | initial version |
adding to what BrianLBall said.
I believe docker prune will only remove data for containers that do not have a reference. So a 0 byte reclaim tells me the containers are stopped but not removed. You may want to check to see all stopped container (docker ps -a) and remove them to start fresh. Removing data within a docker volume (osdata and dbdata) should remove the contents just like if it were on local disk.
Also, /var/lib/docker is the general directory where most docker things are stored. For my use case dunning docker, I've created a separate data volume and mount just for this directory as these can grow quite large. You can also change the path in docker config as well to point to a different path.
We also have a k8s/helm config that can be deployed to the cloud (https://github.com/NREL/OpenStudio-server-helm) that use elastic volumes for db and analysis storage. The disk sizes can be configured and expanded. Running k8s locally though will have the same challenges as docker-compose.
