Vivek Goyal
Vivek Goyal
Right now docker-storage-setup does not allow partition devices in DEVS=. For people who don't use lvm on root disk and don't create a volume group, this can be problematic. Now...
get_docker_storage_options() still seem to be hardcoding DOCKER_STORAGE_OPTIONS. And this will not work for general container storage setup.
Right now d-s-s assumes that system is using lvm and root devices is a logical volume backed by a logical volume group. But that's not the case always. Detect this...
In case of overlay driver, all images and containers will be stored on rootfs. Some might not want that. Hence create options so that docker-storage-setup can prepare a separate volume...
Create some simple automated test cases. Especially for syntax checking of different possible input types.
Right now DATA_SIZE is 60%FREE. That is use 60% of free space for data volume. Dan Walsh was saying that this sounds like a high percentage. It might be a...
Currently our default is to create data volume of size 60%FREE. That is use 60% free space in volume group to create data volume. But on some systems, there is...
Currently if docker-storage-setup fails, docker still starts and falls back to using loopback devices. Is this the right behavior. Or docker should fail to as docker-storage-setup failed. Opening this issue...