Why avoid the shell executor on docker? I did 4years of gitlab back a bit ago. It was super simple. But I haven't kept up since work maintains actions and Travis. And there's a way nowadays to inject the env or pull from a secret server-ish.

All ci is basically the same. Or at least for a while.

[–] azertyfun@sh.itjust.works 1 points 1 week ago (1 children)

Ideally you'd use the docker executor with a dind service instead of docker commands in the shell. You'll have better isolation (e.g. no conflicts from open port forwards) and better forward-compatibility (the pipeline won't break every time a major upgrade is applied to the runner because the docker - especially compose - CLI is unstable).

[–] mesamunefire@piefed.social 1 points 6 days ago

I can see the dependencies mucking everything up.