Update documentation

Signed-off-by: Chris Evich <cevich@redhat.com>
This commit is contained in:
Chris Evich
2022-11-10 11:53:56 -05:00
parent 125d7cb9ac
commit b9e5e066c8

View File

@@ -3,7 +3,11 @@
This container image is built daily from this `Containerfile`, and This container image is built daily from this `Containerfile`, and
made available as: made available as:
* FIXME * `registry.gitlab.com/qontainers/pipglr:latest`
-or-
* `registry.gitlab.com/qontainers/pipglr:<version>`
It's purpose is to provide an easy method to execute a GitLab runner, It's purpose is to provide an easy method to execute a GitLab runner,
to service CI/CD jobs for groups and/or repositories on to service CI/CD jobs for groups and/or repositories on
@@ -30,6 +34,8 @@ configuration, please edit the config.toml file within the
`gitlab-runner-config` volume. `gitlab-runner-config` volume.
Note: These commands assume you have both `podman` and `jq` available. Note: These commands assume you have both `podman` and `jq` available.
Instead of `eval`, if your podman version supports `container runlabel`,
you may use that.
```bash ```bash
$ echo '<registration token>' | podman secret create REGISTRATION_TOKEN - $ echo '<registration token>' | podman secret create REGISTRATION_TOKEN -
@@ -44,6 +50,8 @@ the GitLab runner container may be launched with the following commands.
Note: The first time this is run, startup will take an extended amount Note: The first time this is run, startup will take an extended amount
of time as the runner downloads and runs several (inner) support containers. of time as the runner downloads and runs several (inner) support containers.
As above, instead of `eval`, if your podman version supports `container runlabel`,
you may use that.
Debugging: You may `export PODMAN_RUNNER_DEBUG=debug` to enable inner-podman Debugging: You may `export PODMAN_RUNNER_DEBUG=debug` to enable inner-podman
debugging (or any other supported log level) to stdout. debugging (or any other supported log level) to stdout.