From Fedora Project Wiki
< User:Roshi | QA/AtomicTests
Description
This is a simple testcase to determine whether docker-storage-setup runs correctly after booting an Atomic Host.
Prerequisite
This testcase assumes you have already ran the boot test.
This testcase assumes you have already ran the boot test.
Setup
- Ensure you have a booted working Atomic Host
How to test
- Run the following commands:
# journalctl -o cat --unit docker-storage-setup.service # docker info
Expected Results
- The output of the first command should resemble:
# journalctl -o cat --unit docker-storage-setup.service
Starting Docker Storage Setup...
WARN: sector size not found in sfdisk output, assuming 512
CHANGED: partition=2 start=2099200 old: size=10483712 end=12582912 new: size=39843807,end=41943007
Physical volume "/dev/vda2" changed
1 physical volume(s) resized / 0 physical volume(s) not resized
Size of logical volume atomicos/root changed from <5.00 GiB (1279 extents) to <19.00 GiB (4863 extents).
Logical volume atomicos/root successfully resized.
meta-data=/dev/mapper/atomicos-root isize=512 agcount=4, agsize=327424 blks
= sectsz=512 attr=2, projid32bit=1
= crc=1 finobt=1 spinodes=0 rmapbt=0
= reflink=0
data = bsize=4096 blocks=1309696, imaxpct=25
= sunit=0 swidth=0 blks
naming =version 2 bsize=4096 ascii-ci=0 ftype=1
log =internal bsize=4096 blocks=2560, version=2
= sectsz=512 sunit=0 blks, lazy-count=1
realtime =none extsz=4096 blocks=0, rtextents=0
data blocks changed from 1309696 to 4979712
Started Docker Storage Setup.
- The 'docker info' command output should resemble:
# docker info | grep 'Storage Driver'
Storage Driver: overlay2
WARNING: You're not using the default seccomp profile
- The lsblk command output should resemble:
# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sr0 11:0 1 366K 0 rom vda 252:0 0 6G 0 disk ├─vda1 252:1 0 1G 0 part /boot └─vda2 252:2 0 5G 0 part └─atomicos-root 253:0 0 5G 0 lvm /sysroot