that’s really too bad, I hope that gets resolved soon
that’s a pretty old version of podman (4.3 looks like?); also, why have nested podman? My infra is something like this:
Bare Metal
├─ Rootless Podman
├─ Forgejo
├─ Rootless Forgejo Runner (planning to run on another machine entirely)
├─ <Actions Containers Run Here>
I doubt the extra level of nesting is the issue though. If your issue is networking, then maybe the version of podman is the issue, since they switched out the networking layer in 5.0. I upgraded for a related reason, though I’m still getting some odd issues (mostly w/ the DNS resolver).
I haven’t gotten to cross-compiling just yet, nor have I needed to build a docker image since my projects are very much in the testing phase. But maybe I’ll give it a shot soon, since it’s better to catch these types of issues before it becomes a bigger problem.
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.)
Bare Metal ├─ Rootless Podman ├─ Forgejo ├─ Rootless Forgejo Runner (planning to run on another machine entirely) ├─ <Actions Containers Run Here>I doubt the extra level of nesting is the issue though. If your issue is networking, then maybe the version of podman is the issue, since they switched out the networking layer in 5.0. I upgraded for a related reason, though I’m still getting some odd issues (mostly w/ the DNS resolver).
I haven’t gotten to cross-compiling just yet, nor have I needed to build a docker image since my projects are very much in the testing phase. But maybe I’ll give it a shot soon, since it’s better to catch these types of issues before it becomes a bigger problem.
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.)