Failed to load related branches
Persistent, shared docker daemon for projects/groups
Description
Might be a bad idea, but one way to improve docker caching performance would be to have a persistent docker daemon. This would have to be on a per-project or per-group basis since the docker daemon would have no user-level authentication. It would imply a permanently running instance, which has additional cost, but might be worth it. I could imagine letting people register their docker service, or perhaps pay for us to spin one up for them on Gitlab.com.
Proposal
Replace per-job services (services: [docker:dind]) with a persistent service that is shared between all pipeline runs of a project or even an entire group.