Yep. I'm switching our workflows to instead use regular utilities running inside a Docker container. This works well for _most_ things. There are some issues w

Yep. I'm switching our workflows to instead use regular utilities running inside a Docker container. This works well for _most_ things. There are some issues with doing docker-in-docker for volume mapping, but they're mostly trivial. We're using taskfiles to run tasks, so I can just rely on it for that. It also has a built-in support for nice output grouping ( https://taskfile.dev/docs/reference/schema#output https://taskfile.dev/docs/reference/schema#output ) that Github actions can parse. Pros: 1. Ability to run things in parallel. 2. Ability to run things _locally_ in a completely identical environment. 3. It's actually faster! 4. No vendor lock-in. Offramp to github runners and eventually local runners? Cons: It often takes quite a while to understand how actions work when you want to run them in your own environment. For example, how do you get credentials to access the Github Actions cache and then pass them to Docker? Most of documentation just tells: "Use this Github Action and stop worrying your pretty little head about it".