dustymabe added a new comment to an issue you are following:
``
chrismurphy
Seems reasonable. But I have zero confidence at the moment that ostree can handle a
separate /var file system; it's a question for Colin what assumptions are being made
and I think it assumes it's directory that it bind mounts somewhere, and if it's
really a separate volume, then something has to mount it first before it can be bind
mounted elsewhere.
hmm. so I'm not sure about everything you've said because you've thrown around
some concepts that I might not understand fully. However, what I can do is test. I grabbed
a fedora 25 atomic system and did not allow docker to run on first boot
(`systemd.mask=docker systemd.mask=docker-storage-setup` on kernel command line). I then
did `ostree admin unlock --hotfix` so I could modify the contents of the tree. I then
grabbed latest upstream
[
docker-storage-setup](https://api.github.com/repos/projectatomic/docker-s...
and installed everything to the system with `make install`.
I then configured /etc/sysconfig/docker-storage-setup with:
```
STORAGE_DRIVER=overlay2
DOCKER_ROOT_VOLUME=yes
```
and rebooted the system. Now I get:
```text
-bash-4.3# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sdb 8:16 0 10G 0 disk
sdc 8:32 0 368K 0 disk
sda 8:0 0 20G 0 disk
├─sda2 8:2 0 5.7G 0 part
│ ├─atomicos-docker--root--lv 253:1 0 1.1G 0 lvm /var/lib/docker
│ └─atomicos-root 253:0 0 3G 0 lvm /sysroot
└─sda1 8:1 0 300M 0 part /boot
-bash-4.3#
-bash-4.3# blkid
/dev/sda1: UUID="1cffb3b3-f5c4-4c73-9e4c-adb168f1cefa" TYPE="ext4"
PARTUUID="82b21228-01"
/dev/sda2: UUID="l5jqv8-ZxTX-jIfh-ve4J-aqID-mAZi-O5mU5n"
TYPE="LVM2_member" PARTUUID="82b21228-02"
/dev/mapper/atomicos-root: UUID="96a6e82b-98e5-4ab3-8034-72b61540c166"
TYPE="xfs"
/dev/sdc: UUID="2017-01-09-18-25-56-00" LABEL="cidata"
TYPE="iso9660"
/dev/mapper/atomicos-docker--root--lv:
UUID="3f5ee97d-f612-46c4-abe5-21799e4830b1" TYPE="xfs"
-bash-4.3#
-bash-4.3# docker info
Containers: 0
Running: 0
Paused: 0
Stopped: 0
Images: 0
Server Version: 1.12.5
Storage Driver: overlay2
Backing Filesystem: xfs
Logging Driver: journald
Cgroup Driver: systemd
Plugins:
Volume: local
Network: null host bridge overlay
Swarm: inactive
Runtimes: oci runc
Default Runtime: oci
Security Options: seccomp selinux
Kernel Version: 4.8.15-300.fc25.x86_64
Operating System: Fedora 25 (Atomic Host)
OSType: linux
Architecture: x86_64
Number of Docker Hooks: 2
CPUs: 2
Total Memory: 3.859 GiB
Name: cloudhost.localdomain
ID: YKSF:TWGT:FNJH:B553:F3FK:RFHJ:OUAK:AYOO:T5NP:WBTL:KZFI:MYSY
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry:
https://index.docker.io/v1/
Insecure Registries:
127.0.0.0/8
Registries: docker.io (secure)
```
The mount is handled by `var-lib-docker.mount` systemd file:
```text
-bash-4.3# systemctl cat var-lib-docker.mount
# /etc/systemd/system/var-lib-docker.mount
[Unit]
Description=Mount docker-root-lv on docker root directory.
Before=docker-storage-setup.service
[Mount]
What=/dev/atomicos/docker-root-lv
Where=/var/lib/docker
Type=xfs
Options=defaults
[Install]
WantedBy=docker-storage-setup.service
```
Am I missing something? Did I make some bad assumptions somewhere in this test?
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/186