Forgejo-Runner

[CrazyWolf13]

Name of the Script

forgejo-runner

Script Type

CT (LXC Container)

📋 Script Details

forgejo-runner

[MickLesk]

Only Testable with:

Forgejo Instance URL:
Forgejo Runner Registration Token:

[github-actions]

The forgejo-runner script is ready for testing:
bash -c "$(curl -fsSL https://github.com/community-scripts/ProxmoxVED/raw/main/ct/forgejo-runner.sh)"
Note: This is not in the official repo yet—it's just a dev version! After merging into ProxmoxVE, it will need to be recreated.

[WaffleThief123]

I can handle testing of this, as I run a production forgejo instance. I'll report back here when done!

[WaffleThief123]

so far, found issue: mode=generated (when copying the install from generator) error.

root@pve-testing:~# mode="generated" var_unprivileged="0" var_ctid="<redacted>" var_cpu="12" var_ram="16384" var_disk="128" var_net="static" var_gateway="<redacted>" var_net="<redacted>" var_nesting="1" var_tags="git" var_container_storage="<redacted>" var_template_storage="<redacted>-templates" bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVED/main/ct/forgejo-runner.sh)"


<removed ascii title for brevity>
            
  💡   Running pre-flight checks...

    ✔️   Kernel key limits OK (keys: 65/2000)
    ✔️   Storage with 'rootdir' support available (3 storage(s))
    ✔️   Storage with 'vztmpl' support available (2 storage(s))
    ✔️   Sufficient storage space (<redacted>: 9.7TB free, need 128GB)
    ✔️   Default network bridge vmbr0 available
    ✔️   DNS resolution working
    ✔️   No enterprise repositories enabled
    ✔️   Standalone node (no cluster quorum needed)
    ✔️   LXC stack is up to date (pve-container=6.1.2)
    ✔️   Container IDs available (next: <redacted>)
    ✔️   Template server reachable (download.proxmox.com)
    ✔️   Template available locally for debian 13

  ✔️   All pre-flight checks passed (12/12)
  ✖️  Invalid option: generated

root@pve-testing~# echo $?
1

Based on hitting that, I did the following:

I worked on some fixes for the forgejo-runner script to support mode="generated" (unattended/config generator installs). The current install script references two functions (prompt_input_required and show_missing_values_warning) that don't exist in build.func, which means the install script will fail outright.

Changes in my branch forgejo-runner-fix:

CT script (ct/forgejo-runner.sh):

• Export var_forgejo_instance, var_forgejo_runner_token, and var_runner_labels so they survive the lxc-attach boundary into the container. These are app-specific variables not in build.func's whitelist, so they need explicit exports.

Install script (install/forgejo-runner-install.sh):

• Replaced nonexistent prompt_input_required calls with standard read -r -p prompts (matching the pattern used by pocketid, openziti-controller, etc.)
• Prompts are skipped when variables are already set via environment (generated/unattended mode)
• Added hard error if no runner registration token is provided
• Made runner labels configurable via var_runner_labels — additional labels are appended to the default rather than replacing it
• Updated default runner image from node:20-bookworm to node:22-bookworm (Node 24 is current LTS; Node 22 was chosen to avoid major breaking changes. Node 20 EOL is April 2026)
• Removed call to nonexistent show_missing_values_warning

Example unattended usage:
mode="generated" var_cpu="12" var_ram="16384" var_disk="128" var_forgejo_instance="https://my-forgejo.example.com" var_forgejo_runner_token="MY_TOKEN" var_runner_labels="my-custom:docker://alpine:3" bash -c "$(curl -fsSL ...ct/forgejo-runner.sh)"

I've opened a PR to fix the above: #1645

[WaffleThief123]

Out of sheer curiosity , is there a reason mode=generated (added to ProxmoxVE in PR community-scripts/ProxmoxVE#12807 by @MickLesk on March 12) hasn't been ported to ProxmoxVED's build.func? Right now mode="generated" hits "Invalid option" in ProxmoxVED. Is mode="default" the intended way to do unattended installs here, or should the generated case be synced over?

I'm happy to include the generated mode port in my draft PR #1645 , open a separate PR specifically for it, or leave it for you all to handle. Whatever works best.

[michelroegl-brunner]

@MickLesk Can you do mode generated for dev? I can do it earliest Tuesday next week.

[MickLesk]

maybe next week too. Focus on Bugfixing and little things in main this week

[WaffleThief123]

sounds good! i'll keep an eye on this and mark the related PR #1645 as ready to merge/out of draft status once those changes have been ported over! Thanks Y'all.

[CerberusStyle]

yep this one is a fail.