Skip to content

Conversation

@Mickyleitor
Copy link

This MR will change the following regarding the Ollama Dockerfile:

  • Add zstd package to the apt-get install command
  • Change URL from .tgz to .tar.zst (the correct Ollama download format)
  • Update tar command to use --zstd flag instead of -z (gzip)
  • Add cleanup of apt cache with rm -rf /var/lib/apt/lists/* to reduce image size

- Add zstd package required to decompress .tar.zst files
- Change download URL from .tgz to .tar.zst (correct Ollama format)
- Update tar command to use --zstd flag instead of -z
@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @Mickyleitor, I'm Gemini Code Assist1! 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 refines the Ollama installation process within the Dockerfile by addressing an outdated download format. It ensures that Ollama is successfully installed by incorporating support for the .tar.zst archive, which includes installing the zstd utility and updating the tar extraction command. Additionally, it introduces an optimization to minimize the Docker image footprint by cleaning up the apt cache.

Highlights

  • Ollama Download Format Update: The Ollama download URL has been updated from the .tgz format to the correct .tar.zst format, ensuring the latest version can be properly fetched.
  • Zstd Package Installation: The zstd package is now installed in the Dockerfile, providing the necessary tools to decompress the new .tar.zst archive format.
  • Tar Command Adjustment: The tar command has been modified to use the --zstd flag, correctly extracting the contents of the .tar.zst archive.
  • Docker Image Size Optimization: An apt cache cleanup step (rm -rf /var/lib/apt/lists/*) has been added after package installation to reduce the final Docker image size.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

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.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request correctly fixes the Ollama installation in the Dockerfile by switching to the .tar.zst format. The changes, including adding the zstd package and updating the download and extraction commands, are appropriate. I've added a couple of suggestions to further optimize the Dockerfile by applying common best practices, such as using --no-install-recommends during package installation and piping curl output directly to tar. These changes will help reduce the final image size and improve the build process's efficiency.

Comment on lines 28 to +31
RUN apt-get update && apt-get install -y \
curl
curl \
zstd && \
rm -rf /var/lib/apt/lists/*
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

To optimize the Docker image size and follow best practices, it's recommended to use the --no-install-recommends flag with apt-get install. This prevents the installation of packages that are not strictly necessary for the main packages to function.

RUN apt-get update && apt-get install -y --no-install-recommends \
    curl \
    zstd && \
    rm -rf /var/lib/apt/lists/*

Comment on lines +47 to +49
curl -L "https://ollama.com/download/ollama-linux-${OLLAMA_ARCH}.tar.zst" -o ollama.tar.zst && \
tar --zstd -xf ollama.tar.zst -C /usr && \
rm ollama.tar.zst
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

To improve efficiency and avoid creating an intermediate file on the filesystem, you can pipe the output of curl directly into tar. This makes the command cleaner and avoids the need for a separate rm step.

    curl -L "https://ollama.com/download/ollama-linux-${OLLAMA_ARCH}.tar.zst" | tar --zstd -x -C /usr

@Mickyleitor Mickyleitor marked this pull request as draft January 20, 2026 21:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant