Trying to use overlay2 for storage layer - but using LVM

General Discussions
1

I can’t seem to get over this. I created a logical volume, it’s 58 GB in size. No partition laid down. docker-storage-setup.service

/etc/sysconfig/docker-storage-setup has
STORAGE_DRIVER=overlay2
DEVS=/dev/dm-10

I use that because I get an error when using /dev/mapper/vg_hero1-vg_hero1_lvopt -

There’s really no documentation for the storage service.

I could revert to past hackish solutions like creating a symlink from /var/lib/docker/overlay2 to some filesystem location, but that’s a performance hit.

Can anyone help?

Thanks -
/Bill

2

Maybe this would help -

docker version
Client:
Version: 1.12.6
API version: 1.24
Package version: docker-common-1.12.6-5.git037a2f5.fc25.x86_64
Go version: go1.7.4
Git commit: 037a2f5/1.12.6
Built: Wed Jan 18 12:11:29 2017
OS/Arch: linux/amd64

and:

docker info

Containers: 0
Running: 0
Paused: 0
Stopped: 0
Images: 0
Server Version: 1.12.6
Storage Driver: overlay2
Backing Filesystem: xfs
Logging Driver: journald
Cgroup Driver: systemd
Plugins:
Volume: local
Network: host bridge null overlay
Swarm: inactive
Runtimes: oci runc
Default Runtime: oci
Security Options: seccomp
Kernel Version: 4.9.7-201.fc25.x86_64
Operating System: Fedora 25 (Twenty Five)
OSType: linux
Architecture: x86_64
Number of Docker Hooks: 2
CPUs: 8
Total Memory: 31.07 GiB
Name: hero.hudaceks.home
ID: ZD37:WB2V:HCCB:M4CT:BOKN:C3IF:ACS5:EFFC:RLYI:RCEJ:MS24:OUZ6
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)

3

cant we just use following lines in /etc/docker/daemon.json, instead of block level storage

{
“storage-driver”: “overlay2”
}