Update runner sizes

What does this MR do?

The sizes needed to be updated:

❯ echo $(curl -s https://hub.docker.com/v2/repositories/gitlab%2Fgitlab-runner/tags | jq '.results[] | select(.name=="latest") | .full_size') /2^20 | bc
545

❯ echo $(curl -s https://hub.docker.com/v2/repositories/gitlab%2Fgitlab-runner/tags?page_size=200 | jq '.results[] | select(.name=="alpine-v16.8.1") | .full_size') /2^20 | bc
103

❯ docker pull gitlab/gitlab-runner:latest
latest: Pulling from gitlab/gitlab-runner
Digest: sha256:938a20776072c5ca0d42ebb5e437f27b7dcbd000fa0290e572d6194e35ad40d9
Status: Image is up to date for gitlab/gitlab-runner:latest
docker.io/gitlab/gitlab-runner:latest

❯ docker pull gitlab/gitlab-runner:alpine
alpine: Pulling from gitlab/gitlab-runner
Digest: sha256:930288bf8b56a1dfcdee733a98b6b30e35b9b4c48bd07250d5eb4db822e3ec13
Status: Image is up to date for gitlab/gitlab-runner:alpine
docker.io/gitlab/gitlab-runner:alpine

❯ docker image ls gitlab/gitlab-runner
REPOSITORY             TAG       IMAGE ID       CREATED        SIZE
gitlab/gitlab-runner   latest    b9aa63fdd2b1   25 hours ago   750MB
gitlab/gitlab-runner   alpine    729a4673e87d   26 hours ago   341MB

While alpine is smaller to download, the decompressed size is half of the initial one. Considering that's what actually matters to the people installing images left the actual decompressed size on disk.

Related issues

Author's checklist

• Optional. Consider taking the GitLab Technical Writing Fundamentals course.
• Follow the:
  • Documentation process.
  • Documentation guidelines.
  • Style Guide.
• If you're adding or changing the main heading of the page (H1), ensure that the product tier badge is added.
• If you are a GitLab team member, request a review based on:
  • The documentation page's metadata.
  • The associated Technical Writer.

If you are a GitLab team member and only adding documentation, do not add any of the following labels:

• ~"frontend"
• ~"backend"
• ~"type::bug"
• ~"database"

These labels cause the MR to be added to code verification QA issues.

Reviewer's checklist

Documentation-related MRs should be reviewed by a Technical Writer for a non-blocking review, based on Documentation Guidelines and the Style Guide.

If you aren't sure which tech writer to ask, use roulette or ask in the #docs Slack channel.

• If the content requires it, ensure the information is reviewed by a subject matter expert.
• Technical writer review items:
  • Ensure docs metadata is present and up-to-date.
  • Ensure the appropriate labels are added to this MR.
  • Ensure a release milestone is set.
  • If relevant to this MR, ensure content topic type principles are in use, including:
    • The headings should be something you'd do a Google search for. Instead of Default behavior, say something like Default behavior when you close an issue.
    • The headings (other than the page title) should be active. Instead of Configuring GDK, say something like Configure GDK.
    • Any task steps should be written as a numbered list.
    • If the content still needs to be edited for topic types, you can create a follow-up issue with the docs-technical-debt label.
• Review by assigned maintainer, who can always request/require the above reviews. Maintainer's review can occur before or after a technical writer review.