walters reported a new issue against the project: `atomic-wg` that you are following: `` <vgoyal> walters: so there are two options. One is changing default to overlay2, which is common across all variants <vgoyal> walters: another new option is specifying where the storage from overlayfs comes from. Does it come from root filesystem or from free space in volume group <vgoyal> for atomic, rootfs is just 3G and if we overlayfs uses rootfs, then it will fill up pretty fast. <vgoyal> so we created a new option in dss, DOCKER_ROOT_VOLUME <vgoyal> if one specifies DOCKER_ROOT_VOLUME=yes, then dss looks for free space in volume group and creates a logical volume, makes a file system on this and mounts on /var/lib/docker/ <vgoyal> now when docker starts, it will put all images and containers in the new volume ( and not logical volume backing rootfs) <vgoyal> given workstation rootfs uses all free space, workstation will not require this by default. <vgoyal> but server and atomic leave free space in volume group and by default that can be used for docker. (like devicemapper graph driver) <vgoyal> so DOCKER_ROOT_VOLUME=yes is required only for server and atomic variants only (and not workstation one) `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/186 _______________________________________________ cloud mailing list -- cloud@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to cloud-leave@xxxxxxxxxxxxxxxxxxxxxxx
