942d58d41c
Rather than setting up volumes and starting the pipglr container manually, utilize quadlet + systemd. Retain the old setup and execution method, but move them into separate documentation. Signed-off-by: Chris Evich <cevich@redhat.com>
33 lines
1.1 KiB
Markdown
33 lines
1.1 KiB
Markdown
### Additional Manual steps
|
|
|
|
On systems without Quadlet, some additional steps are required
|
|
to get the pipglr container up and running.
|
|
|
|
### Manual Volume setup
|
|
|
|
Since several users are utilized inside the container volumes must be
|
|
specifically configured to permit access. This is done using several
|
|
*runlabels* as follows:
|
|
|
|
```bash
|
|
$ IMAGE="registry.gitlab.com/qontainers/pipglr:latest"
|
|
$ podman container runlabel setupstorage $IMAGE
|
|
$ podman container runlabel setupcache $IMAGE
|
|
```
|
|
|
|
Note: These volumes generally do not contain any critical operational data,
|
|
they may be re-created anytime to quickly free up host disk-space if
|
|
it's running low. Simply remove them with the command
|
|
`podman volume rm pipglr-storage pipglr-cache`. Then reuse the `setupstorage`
|
|
and `setupcache` *runlabels* as in the above example.
|
|
|
|
#### Manual Runner Startup
|
|
|
|
With the runner configuration saved as a Podman secret, and the runner volumes
|
|
created, the GitLab runner container may be launched with the following commands:
|
|
|
|
```bash
|
|
$ IMAGE="registry.gitlab.com/qontainers/pipglr:latest"
|
|
$ podman container runlabel run $IMAGE
|
|
```
|