From 47b82a7d811bc0f78d95e350def34e7ce72fd328 Mon Sep 17 00:00:00 2001
From: Alex Iribarren <Alex.Iribarren@cern.ch>
Date: Tue, 16 Feb 2021 10:48:31 +0100
Subject: [PATCH] rpmci with good docker image

---
 docs/koji/bootstrapping.md | 9 ++++++++-
 1 file changed, 8 insertions(+), 1 deletion(-)

diff --git a/docs/koji/bootstrapping.md b/docs/koji/bootstrapping.md
index cbd07c8..2f91ae4 100644
--- a/docs/koji/bootstrapping.md
+++ b/docs/koji/bootstrapping.md
@@ -299,6 +299,8 @@ out of it depending on the case. You can use an upstream Docker image to start w
 then eventually replace it, you can build with a different Docker image temporarily,
 you can build the bare minimum RPMs you need by hand... I'm sure you can figure something out.
 
+You may need to temporarily disable the tests of some of the RPMs you'll build later on,
+as they may not work on your Frankenstein'd image.
 
 ## Start building basic packages
 
@@ -456,8 +458,13 @@ Once you have a working Docker image, you can create a scheduled pipeline to
 
 ## Build a new worker image for rpmci
 
+Now that you have a real Docker image for your new distro, you should get rpmci
+to use it. You'll have to build an rpmci worker image based off of it and
+(integrate it)[https://gitlab.cern.ch/linuxsupport/rpmci/-/compare/8e9d5203...db470a66] into rpmci.
 
-
+Once that is done, you can go back through all the previous RPMs you created
+where you had to disable the tests and enable them again. Now that your image is
+good, they should succeed.
 
 ## build cloud image
 
-- 
GitLab