<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=546413) </details> <!--IssueSummary end--> <!--- Please read this! Before opening a new issue, make sure to search for keywords in the issues filtered by the "regression" or "type::bug" label: - https://gitlab.com/gitlab-org/gitlab/issues?label_name%5B%5D=regression - https://gitlab.com/gitlab-org/gitlab/issues?label_name%5B%5D=type::bug and verify the issue you're about to submit isn't a duplicate. ---> ### Summary Running gitlab 18.0.2 with self-hosted gitlab-runne service (18.0.2) in docker with docker volume for config. We started to see longer times for preparations scripts. Example of the same job running in the same runner with different versions: 18.0.2 {width=1095 height=342} 17.10.1 {width=1099 height=333} ### Steps to reproduce Run gitlab-runner 18.0.2 in docker with docker volumes as config and compare with 17 ### What is the current *bug* behavior? Jobs take almost a minute to set the docker executor ### What is the expected *correct* behavior? Docker executor should be ready in seconds