public/pipglr
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Docs update

Browse Source 
Signed-off-by: Chris Evich <cevich@redhat.com>
This commit is contained in:
Chris Evich
2022-11-30 09:42:25 -05:00
parent b591a3d7c5
commit 19a7e501be
1 changed files with 9 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
README.md
View File

@@ -37,17 +37,19 @@ once, prior to registering your runners:
```bash
$ for VOLUME in pipglr-podman-root pipglr-config pipglr-podman-cache; do \
PUPVM="podman unshare podman volume mount $VOLUME"
podman volume create $VOLUME && \
podman unshare chown 1000:1000 $($PUPVM) && \
podman unshare chmod 02770 $($PUPVM) && \
podman unshare ls -land $($PUPVM) ; \
VOLPTH=$(podman unshare podman volume mount $VOLUME)
podman volume create $VOLUME; \
podman unshare chown -R 1000:1000 $VOLPTH && \
podman unshare chmod 02770 $VOLPTH && \
podman unshare ls -land $VOLPTH ; \
podman unshare podman volume unmount $VOLUME ; \
done
```
If you get `podman system service` startup permission-denied errors, or
errors from gitlab-runner, unable to connect to the podman socket, this is
likely the cause. You can fix it after-the-fact using the same commands as above, just add a `-R` option to the `chown`/`chmod`, and additionally target `./*`.
likely the cause. You can fix it after-the-fact using the same commands
above. additionally target `./*`.
#### Runner registration
@@ -107,7 +109,7 @@ sure to use the `podman unshare` command-wrapper to enter the usernamespace.
For example, to display the config:
```bash
$ podman unshare $(podman unshare podman volume mount pipglr-config)/config.toml
$ podman unshare cat $(podman unshare podman volume mount pipglr-config)/config.toml
```
#### Debugging