dev.Dockerfile: use cache mounts to speed up rebuilding

[ZZiigguurraatt]

The branch in #1161 was accidentally deleted and the PR automatically closed, so this PR re-opens it with a new copy of the branch.

• dev.Dockerfile now uses
  cache mounts
  to cache the GOMODCACHE and GOCACHE directories so that dependencies don't
  need to be re-downloaded and re-built every time the image is re-created.
  As a result of this change, dev.Dockerfile now requires
  BuildKit to build. When using
  docker build, this can be enabled by setting the environmental variable
  DOCKER_BUILDKIT=1. BuildKit also does not unnecessarily rebuild images when
  the build context is a remote git repository because COPY layers are more
  smartly compared to cache.

Would like some feedback on this change. Not sure if it might have some unintended consequences that I have not thought of, but it really speeds things up a lot.

[gemini-code-assist]

Summary of Changes

Hello @ZZiigguurraatt, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request focuses on enhancing the build efficiency of the dev.Dockerfile by integrating Docker BuildKit's cache mount capabilities. By caching the GOMODCACHE and GOCACHE directories, the changes aim to drastically reduce the time and resources required for subsequent image rebuilds, as Go dependencies will no longer need to be re-downloaded and re-compiled from scratch. This optimization streamlines the development workflow, though it introduces a dependency on BuildKit for the Docker build process.

Highlights

• dev.Dockerfile Performance Improvement: Implemented Docker cache mounts for GOMODCACHE and GOCACHE in dev.Dockerfile to significantly speed up image rebuilding by caching Go dependencies.
• BuildKit Requirement: The updated dev.Dockerfile now requires Docker BuildKit to be enabled (via DOCKER_BUILDKIT=1) to utilize the new cache mount features.
• Improved COPY Layer Caching: BuildKit's smarter comparison of COPY layers further optimizes rebuilds, especially when the build context is a remote git repository.
• PR Re-opening: This pull request re-opens a previously deleted and automatically closed branch, bringing back the proposed changes.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request introduces a great optimization to the dev.Dockerfile by using cache mounts for Go modules and build cache, which will significantly speed up development builds. The change is well-documented in both the Dockerfile and the release notes. I have one suggestion to further improve Docker layer caching by separating the installation of apk packages into its own RUN layer. This is a minor optimization on top of your existing improvements.