<!--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=536544) </details> <!--IssueSummary end--> MR: Pending ## Description Update the default image to follow the documented precedence for installing dependencies, as documented in https://gitlab.com/gitlab-org/gitlab-build-images/-/tree/master#workspace-image-dependency-installation-order-of-precedence: > ### Workspace image dependency installation order of precedence > > In the workspaces images, a specific order of precedence should be used when installing dependencies, to > prioritize the following goals: > > 1. Prefer built packages rather than building from source > 1. Prefer package managers rather than direct downloads of installation packages or source/tarballs > > The following order of precedence for dependencies should be used: > > 1. **`apt`**: if we don’t care about the version of the dependency. > 1. **`mise`**: > 1. if not available via apt, or > 1. if we care about the version, or > 1. if we want users of the image to be able to easily override the version via `.tool-versions`/`mise.toml`. > 1. **Installation package from dependency's official download site**: if `apt` or `mise` cannot be used for some reason. > 1. **Source built from dependency's official repo or download site**: if installation package doesn’t work for some reason. ## Acceptance criteria TODO: Fill out (required) - [ ] [Describe what must be achieved to complete this issue.] - [ ] [If applicable, please provide design specifications for this feature/enhancement.] - [ ] [If applicable, please list any technical requirements (performance, security, database, etc.)] ## Implementation plan TODO: Fill out or delete (optional) [Provide a high-level plan for implementation of this issue, including relevant technical and/or design details.] <!-- NOTE: Feel free to expand with more sections and headers as needed --> <!-- DO NOT TOUCH BELOW -->