sig_containers/bootc-base-image-build-mirror
4
0
Fork 0
mirror of https://gitlab.com/monolithify/base-image-build.git synced 2024-11-22 03:11:23 +00:00
Code Issues Actions Packages Releases Activity

chore: clarification

Browse Source
This commit is contained in:
Radostin Emanuilov 2024-08-11 20:46:02 +01:00 committed by Radostin Emanuilov
parent b9ab83e8fb
commit 5d2483e34d
1 changed files with 7 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
README.md
View File

@ -1,10 +1,11 @@
## Overview of the pipeline (currently not working) ## Overview of the pipeline (currently not working, use the devcontainer + scripts instead to build it)
1. A Cloud VM Rocky Linux disk is downloaded, then customized so it can run docker inside 1. A Cloud VM Rocky Linux disk is downloaded, then customized so it can run docker inside
2. A Rocky Linux bootc repo is cloned onto that and the repo is used to build a Rocky Linux 9.4 bootc Docker image, which is then uploaded to a container registry, the pipeline for that is here due to `1.` and `2` sharing files and its easier to debug them if needed like this 2. A Rocky Linux bootc repo is cloned onto that and the repo is used to build a Rocky Linux 9.4 bootc Docker image, which is then uploaded to a container registry, the pipeline for that is here due to `1.` and `2` sharing files and its easier to debug them if needed like this
#### !!! IMPORTANT !!! The pipeline assumes that the Gitlab runner host has a shared a directory called `/rockyDisks` that can be used by all jobs and persists between runs/jobs, otherwise you'd need to make a change in some of the `build-builder-vm-disk` step's files so that the builder VM disk is generated/the step is triggered #### !!! IMPORTANT !!! The pipeline assumes that the Gitlab runner host has a shared a directory called `/rockyDisks` that can be used by all jobs and persists between runs/jobs, otherwise you'd need to make a change in some of the `build-builder-vm-disk` step's files so that the builder VM disk is generated/the step is triggered
### To run a new build of the Cloud VM image change the ### To run a new build of the Cloud VM image change the
## To run this inside a VS Code dev container ## To run this inside a VS Code dev container
@ -18,6 +19,7 @@ To download and setup a Rocky Linux VM Disk that is to be used for building a bo
``` ```
3. To build a bootc container image and push it, fill out the CONTAINER_REGISTRY vars below, then run: 3. To build a bootc container image and push it, fill out the CONTAINER_REGISTRY vars below, then run:
``` ```
export CONTAINER_REGISTRY_RW_USER=someuser export CONTAINER_REGISTRY_RW_USER=someuser
export CONTAINER_REGISTRY_RW_PASS=some_api_key export CONTAINER_REGISTRY_RW_PASS=some_api_key
@ -25,11 +27,13 @@ export CONTAINER_REGISTRY_RW_PASS=some_api_key
``` ```
### If any debugging is needed you can connect to the latest builder disk run the following, note all changes will be saved: ### If any debugging is needed you can connect to the latest builder disk run the following, note all changes will be saved:
``` ```
./scripts/debug/main.sh ./scripts/debug/main.sh
``` ```
To connect to a specific builder disk run To connect to a specific builder disk run
``` ```
./scripts/debug/main.sh /base-image-build/local.qcow2 ./scripts/debug/main.sh /base-image-build/local.qcow2
``` ```