From Fedora Project Wiki
(update for f28)
Line 7: Line 7:
 
# Run a dockerized application
 
# Run a dockerized application
 
# Example:
 
# Example:
  docker run -it --rm busybox true && echo "PASS" || echo "FAIL"
+
  docker run -it --rm docker.io/busybox true && echo "PASS" || echo "FAIL"
 
|results=
 
|results=
 
# Output from the example command should resemble:
 
# Output from the example command should resemble:
  Unable to find image 'busybox' locally
+
  <nowiki>
Pulling repository busybox
+
# docker run -it --rm docker.io/busybox true && echo "PASS"
e72ac664f4f0: Download complete
+
Unable to find image 'docker.io/busybox:latest' locally
511136ea3c5a: Download complete  
+
Trying to pull repository docker.io/library/busybox ...
df7546f9f060: Download complete
+
sha256:58ac43b2cc92c687a32c8be6278e50a063579655fe3090125dcb2af0ff9e1a64: Pulling from docker.io/library/busybox
e433a6c5b276: Download complete
+
f70adabe43c0: Pull complete  
PASS
+
Digest: sha256:58ac43b2cc92c687a32c8be6278e50a063579655fe3090125dcb2af0ff9e1a64
# Ensure that the docker daemon is using the storage set up by container-storage-setup
+
Status: Downloaded newer image for docker.io/busybox:latest
  $ lsblk  
+
PASS
NAME                         MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
+
</nowiki>
vda                          252:0    0   20G 0 disk
+
 
└─vda1                        252:1   0    20G  0 part
+
# Ensure that the docker daemon is using the overlay2 storage driver set up by container-storage-setup
vdb                          252:16  0    6G  0 disk  
+
  <nowiki>
├─vdb1                        252:17  0   300M 0 part /boot
+
# lsblk
└─vdb2                        252:18  0   5.7G 0 part  
+
NAME             MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
  ├─atomicos-root             253:0    0     4G 0 lvm  /sysroot
+
sr0                11:0    1  366K  0 rom  
  └─atomicos-docker--root--lv 253:1    0  1.1G  0 lvm  /sysroot/ostree/deploy/fedora-atomic/var/lib/docker
+
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
 +
# docker info | grep Storage
 +
Storage Driver: overlay2
 +
</nowiki>
 
}}
 
}}

Revision as of 02:28, 11 April 2018

Description

This is a simple testcase to determine whether docker containers run properly on an Atomic Host.

Note.png
Prerequisite
This testcase assumes you have already ran the boot test.

Setup

  1. Ensure you have a booted working Atomic Host

How to test

  1. Run a dockerized application
  2. Example:
docker run -it --rm docker.io/busybox true && echo "PASS"

Expected Results

  1. Output from the example command should resemble:
# docker run -it --rm docker.io/busybox true && echo "PASS"
Unable to find image 'docker.io/busybox:latest' locally
Trying to pull repository docker.io/library/busybox ... 
sha256:58ac43b2cc92c687a32c8be6278e50a063579655fe3090125dcb2af0ff9e1a64: Pulling from docker.io/library/busybox
f70adabe43c0: Pull complete 
Digest: sha256:58ac43b2cc92c687a32c8be6278e50a063579655fe3090125dcb2af0ff9e1a64
Status: Downloaded newer image for docker.io/busybox:latest
PASS

  1. Ensure that the docker daemon is using the overlay2 storage driver set up by container-storage-setup
# 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
# docker info | grep Storage
Storage Driver: overlay2