Help from #podman or #docker users welcome!

We have started to offer open alpha access to a hosted Forgejo Actions CI runner. Unfortunately, there are many jobs that can crash the runner for every user reliably, and many users execute them inadvertently.

To save cost and disk wear, we want to keep temporary writes inside the CI builds in RAM and only store the images persistently.

However, the setup is apparently incorrect and we need help figuring it out.

See codeberg.org/actions/meta/issu…

Help with the setup appreciated

Currently, I am the only person actively maintaining the setup, with occasional help from some others for debugging. However, the setup turned out to be more complicated than I anticipated and I would be happy to receive assistance.

^Codeberg.org