Monorepo for building and publishing multiple Docker containers as microservices within a single repository.

FuzzOS

• Table of Contents
  • What is Orion?
  • How does it operate?
  • Build Instructions and Development
    • Usage
    • Testing
    • Known Issues
    • error creating overlay mount to /var/lib/docker/overlay2/<...>/merged: device or resource busy
  • Architecture

Orion is a build environment for services we run in our Fuzzing infrastructure (i.e LibFuzzer) and home of FuzzOS a multipurpose image which most of our fuzzing services use as a base.

For spawning a cluster of Docker containers at EC2 or other cloud providers, see the parent project Laniakea.

CI and CD are performed autonomous with Travis and the Monorepo manager script. A build process gets initiated only if a file of a particular service has been modified and only then will that service will be rebuilt; other services are not affected from the build service at the time except during cron tasks where all images are rebuilt. Each image is either tagged with the latest revision, nightly or latest before being published to the Docker registry. For more information about each service take a look in the corresponding README.md of each service or check out the Wiki pages for FAQs and a Docker cheat sheet.

You can build, test and push locally, which is great for testing outside of Travis. In order to do that run the command below and adjust the path to the service you want to interact and the repository DOCKER_ORG to which you intent to push. DOCKER_ORG is used as tag name for the image.

Note that you might want to edit the service.yaml of the image too, if you intent to make use of custom build_args, parent images and manifest destinations.

#!/usr/bin/env bash
export DOCKER_ORG=<DOCKER_USERNAME>
export TRAVIS_PULL_REQUEST=false
export TRAVIS_BRANCH=master
export TRAVIS_EVENT_TYPE=cron
./monorepo.py -ci travis -build -test -deliver -path core/linux
./monorepo.py -ci travis -build -test -deliver -path base/linux/fuzzos

make help

Before a build task is initiated in Travis CI, each Shellscript and Dockerfile undergo a linting process which may or may not abort each succeeding task. To ensure your Dockerfile passes, you are encouraged to run make lint before pushing your commit.

Each service folder may contain a tests folder in which Container Structure Tests are defined. The Monorepo Manager will run these tests with the -test flag set in the CI after the build process is completed and before deploying the images to the registry. To ensure your modifications to a Dockerfile and/or recipes did not cause breakage, you are encouraged to run make test before pusing your commit.

Workaround: docker/for-linux#711

$ sudo systemctl stop docker
$ sudo nano /etc/docker/daemon.json
{
  "max-concurrent-uploads": 1
}
$ sudo systemctl start docker
$ docker push [...]