You could flip the breaker off for the well to find out.

Once there’s no more pressure from the well, if the irrigation system keeps pressure, you know wherever that water comes from, it’s not your hole.

I agree that it is quite possibly related to the version of Podman moreso than an inherent issue. I am currently satisfied, however, and have no desire to fiddle with it any more… Or at least until Debian 13 gets released.

My use of PinP is almost entirely for cleanliness. It allows me to more easily wipe the build environment (clear out space, troubleshooting). It also mildly improves security as the ‘untrusted’ actions containers run on a separate environment from the important Forgejo container.

The workaround I use for the premade Docker actions not functioning is to simply install Podman as one of the build steps and use that instead, lol. (Some configuration required, but that’s the gist.)

Forgejo Actions is definitely not a turnkey idential-to-GitHub solution, but it’s quite similar and for most not-super-complicated setups it’s basically the same (for better or worse, depending on if you like GH’s Actions).

As far as I remember, everything that I need works out of the box, except for Docker. In fact, just about everything Docker is somewhat quirky in Forgejo Actions.

1. One mildly annoying quirk of Forgejo is that as of current, the token generated for each Actions run is not quite the same as GitHub’s token. For my specific use case, if you want to upload a Docker Image to the package repository, you can not use the standard auto-generated token, which GitHub does allow you to use. Forgejo instead currently requires you generate your own app token and use that instead, as the auto-generated one lacks permissions over packages. (https://codeberg.org/forgejo/forgejo/issues/3571)

2. Depending on your infrastructure, it might just be impossible to make the various Docker-related actions (such as https://code.forgejo.org/docker/build-push-action) work. As an example, my infrastructure outlined below is one such case where those actions simply do not work.

Bare Metal (Debian 12) /
├─ Rootless Podman/
   ├─ Forgejo
   ├─ Forgejo Runner
   ├─ Podman-in-Podman (Inner Podman also Rootless)/
      ├─ <Actions Containers Run Here>

* If you use rootful Docker with Docker-in-Docker, those actions will then work as expected. It is just that attempting to make them work with Rootless Podman (at least the version that ships with Debain 12) currently seems to be impossible.

I was joking with some friends about doing exactly this. Schuck it down to just the battery and minimal drivetrain, and make a very heavy go-kart.

Arch, because I use niche software and the AUR doesn’t always get along with Manjaro very well (ungoogled-chromium-bin is the worst offender). Switched to arch, configured it identically to my manjaro install, and all has been well.

Firefox (well, librewolf, but forks are a matter of personal preference).

Chrome (Ungoogled chromium) is used as a fallback for the occasional site that doesn’t work with my restrictive FF configuration.

Both have uBlock, though they’re configured differently to suit their individual purposes.