Use the Silo image in the cache server setup steps

Andrew Dunnrequested to merge
docs/minio-silo-cache-image into main

What does this MR do?

On a host without a cached image, the docker run step in Use MinIO now fails at the pull. Docker Hub no longer serves minio/minio, so the pull is denied.

This MR changes the image in that command to pgsty/silo:latest. Silo is a fork of MinIO. It reads the same MINIO_ROOT_USER and MINIO_ROOT_PASSWORD variables and serves on the same port, so the other steps stay as they are.

The section also sends readers to an S3 cache example that sets Insecure = false. This server speaks HTTP without TLS, and the runner builds an https endpoint unless Insecure is true (cacheconfig.go), so the page now says to set Insecure = true.

The same swap landed in the GitLab QA project: gitlab-qa!1463 (merged)

Silo keeps the image arguments, variables and data directory, so it drops in. Garage, which the chart migration guide uses, needs layout, key and bucket commands, so this section would become a rewrite. Silo is AGPL-3.0, like MinIO.

Related issues

None.

How it was checked

On a test VM with Docker Engine 29.9.1 and GitLab Runner 19.5.0, following the page's steps:

  • With minio/minio:latest, docker run stops at the pull: pull access denied for minio/minio, repository does not exist or may require 'docker login'. Pulling alpine:latest on the same host works.
  • With pgsty/silo:latest, the container starts. /minio/health/live returns 200, and an anonymous request to the bucket returns 403.
  • A docker executor runner with [runners.cache] set as in the distributed runners caching example, pointed at that server, uploaded a cache in the first job (Uploading cache.zip, Created cache). The second job restored it (Successfully extracted cache).
  • With Insecure = true the runner reached the server over HTTP and cached.
  • Vale and markdownlint-cli2 with this project's configuration report no finding on the changed lines, and lychee's offline link check reports no errors on the page.

Author's checklist

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.

An AI coding assistant wrote this change. It also ran the steps above on a test VM, and ran Vale, markdownlint-cli2 and lychee with this project's configuration on a local workstation.

Merge request reports