search

minishift / minishift-centos-iso

CentOS based ISO as an alternative for boot2docker ISO
GNU Lesser General Public License v3.0
40 stars 33 forks source link

Issue #73 Add overlay as storage driver for docker instead devicemapper #207

Closed praveenkumar closed 6 years ago

praveenkumar commented 6 years ago

Fix #73

praveenkumar commented 6 years ago

retest this please

praveenkumar commented 6 years ago

retest this please

LalatenduMohanty commented 6 years ago

I tested the ISO from http://artifacts.ci.centos.org/minishift/minishift-centos-iso/pr/207/ and still see device mapper in use. What am I missing?

$ sha256sum minishift-centos7.iso
b9ccf3d51e79c50cb88ca0ff97e3f7697af03beaa24f2c6bb8652d4de0f9e9d0  minishift-centos7.iso
$ docker info
Containers: 7
 Running: 5
 Paused: 0
 Stopped: 2
Images: 5
Server Version: 1.12.6
Storage Driver: devicemapper
 Pool Name: docker-8:1-8393767-pool
 Pool Blocksize: 65.54 kB
 Base Device Size: 10.74 GB
 Backing Filesystem: xfs
 Data file: /dev/loop5
 Metadata file: /dev/loop6
 Data Space Used: 1.355 GB
 Data Space Total: 107.4 GB
 Data Space Available: 18.39 GB
 Metadata Space Used: 2.212 MB
 Metadata Space Total: 2.147 GB
 Metadata Space Available: 2.145 GB
 Thin Pool Minimum Free Space: 10.74 GB
 Udev Sync Supported: true
 Deferred Removal Enabled: true
 Deferred Deletion Enabled: true
 Deferred Deleted Device Count: 0
 Data loop file: /var/lib/docker/devicemapper/devicemapper/data
 WARNING: Usage of loopback devices is strongly discouraged for production use. Use `--storage-opt dm.thinpooldev` to specify a custom block storage device.
 Metadata loop file: /var/lib/docker/devicemapper/devicemapper/metadata
 Library Version: 1.02.140-RHEL7 (2017-05-03)
Logging Driver: journald
Cgroup Driver: systemd
Plugins:
 Volume: local
 Network: null bridge host overlay
Swarm: inactive
Runtimes: runc docker-runc
Default Runtime: docker-runc
Security Options: seccomp selinux
Kernel Version: 3.10.0-693.17.1.el7.x86_64
Operating System: CentOS Linux 7 (Core)
OSType: linux
Architecture: x86_64
Number of Docker Hooks: 3
CPUs: 2
Total Memory: 1.953 GiB
Name: minishift
ID: RU4D:WUHL:5KDG:RRSR:FDJH:SHCX:S7QD:SZJE:O5YD:TK55:YS7V:YLUK
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
WARNING: bridge-nf-call-ip6tables is disabled
Labels:
 provider=kvm
Insecure Registries:
 172.30.0.0/16
 127.0.0.0/8
Registries: docker.io (secure)
praveenkumar commented 6 years ago

I tested the ISO from http://artifacts.ci.centos.org/minishift/minishift-centos-iso/pr/207/ and still see device mapper in use. What am I missing?

Yes you are, you can't test this ISO with current minishift master or released version, you need to take http://artifacts.ci.centos.org/minishift/minishift/pr/1961/ artifacts from https://github.com/minishift/minishift/pull/1961 PR.

LalatenduMohanty commented 6 years ago

@praveenkumar After using the minishift binary from the PR it works for me now.

 docker info
Containers: 7
 Running: 6
 Paused: 0
 Stopped: 1
Images: 5
Server Version: 1.12.6
Storage Driver: overlay2
 Backing Filesystem: xfs
 Native Overlay Diff: true
Logging Driver: journald
Cgroup Driver: systemd
Plugins:
 Volume: local
 Network: host overlay null bridge
Swarm: inactive
Runtimes: docker-runc runc
Default Runtime: docker-runc
Security Options: seccomp selinux
Kernel Version: 3.10.0-693.17.1.el7.x86_64
Operating System: CentOS Linux 7 (Core)
OSType: linux
Architecture: x86_64
Number of Docker Hooks: 3
CPUs: 2
Total Memory: 1.953 GiB
Name: minishift
ID: QNDF:WLZU:ND3Z:RI5C:GHA3:ZAXV:LQK6:4O3E:6OG5:FXSL:KCFO:CFW7
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
WARNING: bridge-nf-call-ip6tables is disabled
Labels:
 provider=kvm
Insecure Registries:
 172.30.0.0/16
 127.0.0.0/8
Registries: docker.io (secure)