hyperreal/vauxite-build
1
0
Fork 0
mirror of https://codeberg.org/hyperreal/vauxite-build synced 2024-11-01 16:53:12 +01:00
Code Issues Actions Packages Projects Releases Wiki Activity

Update README.org

Browse Source
This commit is contained in:
Jeffrey Serio 2024-03-06 20:16:36 -06:00
parent 5d2a2254e1
commit 29e605c4eb
1 changed files with 0 additions and 86 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

86
README.org
View File

@ -39,92 +39,6 @@ The ~vauxite.json~ treefile and under the ~src~ directory contains my personal c
We should now be ready to use the Podman runner.
*** Setup Podman-in-Podman runner
To get the [[https://gitlab.com/qontainers/pipglr][Podman-In-Podman]] runner working for a self-hosted GitLab instance, we need to clone the repository and build a custom image passing the GitLab instance URL as a build argument.
1. Login to the right container registry.
#+begin_src shell
podman login -u hyperreal -p <registry api token> git.hyperreal.coffee:5050
#+end_src
2. Clone, build, and push to registry.
#+begin_src shell
git clone https://gitlab.com/qontainers/pipglr
cd pipglr
podman build --env GITLAB_URL=https://git.hyperreal.coffee -t git.hyperreal.coffee:5050/fedora-atomic/containers/pipglr:latest .
podman push git.hyperreal.coffee:5050/fedora-atomic/containers/pipglr:latest
#+end_src
3. Create a new runner from the GitLab UI.
4. Use the authentication token from the GitLab UI to create a podman secret.
#+begin_src shell
echo '<token>' | podman secret create REGISTRATION_TOKEN -
#+end_src
5. Ensure ~config.toml~ exists in the current working directory.
#+begin_src shell
touch ./config.toml
#+end_src
6. Use the custom image we pushed to the container registry.
#+begin_src shell
IMAGE="git.hyperreal.coffee:5050/fedora-atomic/containers/pipglr:latest"
#+end_src
7. Register the runner.
#+begin_src shell
podman container runlabel register $IMAGE
#+end_src
8. Edit ~config.toml~ to use the custom Fedora image from this project.
#+begin_src toml
[runners.docker]
image = "git.hyperreal.coffee:5050/fedora-atomic/containers/fedora:latest"
#+end_src
9. Setup the storage and cache volumes.
#+begin_src shell
podman container runlabel setupstorage $IMAGE
podman container runlabel setupcache $IMAGE
#+end_src
10. Create a podman secret using ~config.toml~.
#+begin_src shell
podman secret create config.toml ./config.toml
#+end_src
11. Run the runner.
#+begin_src shell
podman container runlabel run $IMAGE
#+end_src
12. Enable the runner user to run services after logout:
#+begin_src shell
sudo loginctl enable-linger $(id -u)
#+end_src
The new Podman-In-Podman runner should now appear in the GitLab UI.
**** Expand user namespace
1. pipglr excludes three UID/GIDs from being used by job-level containers. One for each of root, podman, and runner users. Since most distributions set ~65536~ as the default maximum number of IDs to allocate for user namespaces (via ~/etc/login.defs~), distribution images that assign essential users a high UID/GID will fail to setup the namespace for pipglr jobs. The workaround to this is increasing the UID/GID limit on the host by three. See [[https://gitlab.com/qontainers/pipglr/-/blob/main/root/setup.sh?ref_type=heads#L86]]
~/etc/subuid~ and ~/etc/subgid~:
#+begin_src shell
jas:100000:65539
#+end_src
2. Make the changes take effect.
#+begin_src shell
podman system migrate
#+end_src
For debugging purposes:
#+begin_src shell
podman logs --since 0 pipglr
#+end_src
It may be necessary to build a custom pipglr image with more verbose logging. The ~runner.service~ and ~podman.service~ files have ~log-level~ options that can be set to "debug".
*** Notes about ~.gitlab-ci.yml~
- The package ~container-selinux~ is required for the vauxite-compose-job so SELinux works inside the runner container. I'm considering having a custom image built on a weekly basis from registry.fedoraproject.org/fedora:latest that contains updated packages and the required dependencies, which I would then just use as the runner's container image. The registry.fedoraproject.org/fedora:latest image doesn't seem to be updated at all. See [[https://git.hyperreal.coffee/fedora-atomic/containers]]
- BUILD_REPO and SOURCE_REPO are the directories ~/build-repo~ and ~/source-repo~. If these values are changed, then we would need make equivalent changes to the ~volumes~ directive in ~/etc/gitlab-runner/config.toml~ if we want to keep persistent storage of those repos across pipeline runs. Eventually there will be a conditional in the ~.gitlab-ci.yml~ to clean these volumes if another variable (say CLEAN_BUILD) is set to true.