Compare commits

..

4 commits

Author SHA1 Message Date
5c658db776
Add demo WF for IpPv6 test
Some checks are pending
/ ipv6 (push) Waiting to run
2025-01-07 17:42:07 +01:00
3a84de38cb
Add note on IPv6 support 2025-01-07 17:38:17 +01:00
dbaaa0a16a
Remove automatic cleanup section because it does not work
- No systemd session is available for podman in crontab entries and there appears to be no proper way to get one without a PTY...
2025-01-07 17:34:35 +01:00
b47e670e0b
Start podman socket immediately 2025-01-07 16:53:31 +01:00
3 changed files with 19 additions and 10 deletions

View file

@ -6,3 +6,6 @@ insert_final_newline = true
charset = utf-8
indent_style = space
indent_size = 4
[*.yml]
indent_size = 2

View file

@ -0,0 +1,14 @@
---
on:
push:
branches:
- main
workflow_dispatch:
jobs:
ipv6:
runs-on: docker
steps:
- run: |
apt update; apt install --yes curl
curl -s -o /dev/null https://ipv6.google.com

View file

@ -33,19 +33,10 @@ machinectl shell --uid forgejo-runner # <-- This is basically "sudo -Hi XXX" but
```
```bash
systemctl enable --user podman.socket
systemctl --user enable --now podman.socket podman
echo 'export DOCKER_HOST=unix://$XDG_RUNTIME_DIR/podman/podman.sock' >> ~/.profile
```
#### Automatic podman cleanup on reboot
```bash
crontab -e
```
```cronexp
@reboot podman system cleanup --all --force
```
### 4. Install the forgejo-runner
```bash
@ -74,6 +65,7 @@ Or, if you're volunteering another runner for our instance, please contact us to
```bash
# As forgejo-runner
forgejo-runner generate-config > config.yml
# You should open the config.yml and enable IPv6 support! (Your cloud host might charge extra for IPv4 connectivity)
# We're about to enter secrets into the terminal, disable history:
set +o history