@WoodpeckerCI the biggest point of friction for me is that you cannot simply run docker itself in the standard docker based runner setup, making it awkward to embrace something like testcontainers or other ad-hoc scripts that run docker: all such workflows need to be translated and duplicated into equivalent woodpecker plugins/steps. That wouldn't be so bad if woodpecker offered a standalone runner that could run on a dev machine and execute flows locally as part of the developer iteration loop.