tree: e93fc41931a9d36f42ed041b7cd75d23c6fa821b [path history] [tgz]
  1. cloudbuild.yaml
  2. Dockerfile

COS Xfstests Runner container used in COS xfstests


This is an docker image used by COS (Container-Optimized OS) xfstests. It includes scripts and necessary dependencies for running gce-xfstests under a given xfstests config against a given COS version.

The image is released at with a unique tag for each release. This container image is not publicly available.

Building COS Xfstests Runner Image

Locally (for testing the image)

For testing, you can simply build and test this docker container locally on your workstation:

  $ docker build -t cos-xfstests-runner:dev .

Production (push into GCR)

Since is not publicly available, only authenticated users can push into the GCR registry.

  $ VERSION=<version>  # e.g., 20171008
  $ docker build -t$VERSION .
  $ docker build -t .
  $ gcloud docker -- push$VERSION
  $ gcloud docker -- push

Using COS Xfstests Runner Image

Locally (for testing the image)

COS xfstests runner container will use the xfstests-bld tarball and kernel image generated by COS kernel CI. To run this container locally, you can build the kernel image using cos_kerenl_devenv container.

To run the COS xfstests runner locally:

  $ docker run --rm -v ~/.config/gcloud:/root/.config/gcloud cos-xfstests-runner:dev -x overlay -n xfs-vm -r gs://xueweiz-play/xfstests/R76-12188.0.0 -p cos-xfstests -z us-west1-c -b generic/269,generic/347,generic/405,generic/500

The container will download xfstests-bld tarball and kernel image from given GCS bucket, then run gce-xfstests script on the given config. This will create one GCE instance and two responding disks in the given project and zone. If they run into soft lockup, the developer must manually clean them up.

The container image is set to use test appliance image “xfstests-201901211635” by default. Use the --rootfs_image to overwrite it.