container-storage-setup
container-storage-setup copied to clipboard
Service to set up storage for Docker and other container systems
should setting `CONTAINER_ROOT_LV_MOUNT_PATH` also update docker to not point at `/var/lib/docker` ?
I set: ``` STORAGE_DRIVER=overlay2 GROWPART=true ROOT_SIZE=15G CONTAINER_ROOT_LV_SIZE=100%FREE CONTAINER_ROOT_LV_NAME="container-root-lv" CONTAINER_ROOT_LV_MOUNT_PATH="/var/lib/containers/container-runtime" ``` I want `/var/lib/containers/container-runtime` to be used by docker. Should container-storage-setup do this for me?
Hi, We are using Atomic Host CentOS on our systems in the field to run our docker application containers. We are also running cockpit to have easy access to system...
See https://github.com/projectatomic/container-storage-setup/pull/105#issuecomment-355712676 Fails as `ERROR: Partition specification unsupported at this time.`
I'm getting issues with the docker service after reboot, (specifically a `cannot take ownership of /vart/lib/docker` error in journalctl). After doing some digging, it appears to be some systemd configurations...
Currently, docker-storage-setup assumes that the default location of the "root" filesystem for Docker images/containers to be at "/var/lib/docker". What if I want it to be at another place via "-g"...
If people use CONTAINER_ROOT_LV_MOUNT_PATH for c-s-s to mount docker runtime storage into places other than /var/lib/docker, they expect that selinux file labels there are set correctly.
Following the [RHEL documentation](https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux_atomic_host/7/html/managing_containers/managing_storage_with_docker_formatted_containers#overlay_graph_driver) for setting up the `overlay2` graph driver, which recommends: ``` CONTAINER_ROOT_LV_MOUNT_PATH=/var/lib/docker ``` `atomic storage reset` subsequently fails with ``` rm: cannot remove ‘/var/lib/docker’: Device or resource...
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...
Signed-off-by: Shishir Mahajan
Now that you can use parted for managing the partitions (#191), would it be possible to switch to GPT instead of MBR? This would help addressing #114. This will require...