Skip to content

Refresh bench tooling and Claude profiles#1

Open
brettheap wants to merge 1 commit into
mainfrom
agent/bench-refresh-2026-07
Open

Refresh bench tooling and Claude profiles#1
brettheap wants to merge 1 commit into
mainfrom
agent/bench-refresh-2026-07

Conversation

@brettheap

@brettheap brettheap commented Jul 13, 2026

Copy link
Copy Markdown
Contributor

Summary

  • mount portable Claude account profiles where applicable
  • refresh the bench-specific runtime and administration toolchain
  • keep the bench aligned with the synchronized workBenches parent

Validation

  • git diff --check
  • changed shell scripts: bash -n
  • changed Dockerfile: docker buildx build --check

Summary by Sourcery

Refresh bench Docker layer2 image to align with updated tooling and portable Claude profiles.

Copilot AI review requested due to automatic review settings July 13, 2026 00:14
@brettheap

Copy link
Copy Markdown
Contributor Author

@codex review

@sourcery-ai

sourcery-ai Bot commented Jul 13, 2026

Copy link
Copy Markdown
Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

This PR refreshes the layer-2 bench Docker image to align with the updated bench runtime/tooling and to mount portable Claude profiles where applicable.

File-Level Changes

Change Details Files
Update the layer-2 bench Docker image to use refreshed runtime/tooling and support portable Claude profiles.
  • Adjust base image and/or runtime dependencies to match the synchronized workBenches parent.
  • Update build/runtime environment configuration to integrate portable Claude account profiles.
  • Refresh admin/bench-specific tooling installed or configured in the image.
  • Clean up or modernize Dockerfile directives to align with current best practices and parent bench setup.
Dockerfile.layer2

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

@sourcery-ai sourcery-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Hey - I've reviewed your changes and they look great!


Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Pull request overview

Updates the Layer 2 frappe-bench container image definition to align with refreshed bench tooling assumptions (especially what’s provided by the parent/base images) and to adjust how the Python bench toolchain is installed/verified.

Changes:

  • Bumped Layer 2 image version metadata.
  • Removed in-image Docker CLI/Compose installation and replaced it with a build-time verification step.
  • Refreshed Python tooling install by pinning several dependencies and installing frappe-bench separately with --no-deps, plus added uv/bench version checks.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread Dockerfile.layer2
&& curl -fsSL -o /usr/local/lib/docker/cli-plugins/docker-compose \
https://github.com/docker/compose/releases/download/v2.34.0/docker-compose-linux-x86_64 \
&& chmod +x /usr/local/lib/docker/cli-plugins/docker-compose
RUN docker --version && docker compose version
Comment thread Dockerfile.layer2
Comment on lines +83 to +85
'setuptools>=71.0.0,<82.0.0' \
&& pip3 install --break-system-packages --no-deps frappe-bench \
&& pip3 cache purge \
Comment thread Dockerfile.layer2
Comment on lines +12 to 13
LABEL layer.version="2.1.3"
LABEL layer.updated="2026-03-07"

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 07eabe25ce

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread Dockerfile.layer2
'python-crontab~=2.6.0' \
'requests~=2.33.0' \
'setuptools>=71.0.0,<82.0.0' \
&& pip3 install --break-system-packages --no-deps frappe-bench \

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P1 Badge Install semantic-version with bench

Because this image now installs frappe-bench with --no-deps, every runtime dependency has to be listed explicitly. The added list omits semantic-version, which current bench imports from bench.app; the later bench get-app commands in this same Dockerfile load that module, so the Layer 2 build will fail with ModuleNotFoundError: No module named 'semantic_version' before the template apps are fetched.

Useful? React with 👍 / 👎.

Comment thread Dockerfile.layer2
&& curl -fsSL -o /usr/local/lib/docker/cli-plugins/docker-compose \
https://github.com/docker/compose/releases/download/v2.34.0/docker-compose-linux-x86_64 \
&& chmod +x /usr/local/lib/docker/cli-plugins/docker-compose
RUN docker --version && docker compose version

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 Badge Install the Docker client instead of only checking it

When this repo is built against the documented dev-bench-base:latest Layer 1a that does not already provide Docker Compose, this replaces the only Layer 2 Docker client installation with a version check. The devcontainer bind-mounts /var/run/docker.sock, but that mount does not provide the docker or Compose binaries, so bases without those tools now fail at this RUN step instead of producing the Frappe image.

Useful? React with 👍 / 👎.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 07eabe25ce

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread Dockerfile.layer2
'python-crontab~=2.6.0' \
'requests~=2.33.0' \
'setuptools>=71.0.0,<82.0.0' \
&& pip3 install --break-system-packages --no-deps frappe-bench \

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P1 Badge Install semantic-version before bench get-app

In a clean Layer 1a image that does not already have semantic-version, installing frappe-bench with --no-deps skips one of bench's declared runtime dependencies. The template build later runs bench get-app, which imports bench.app and then semantic_version, so the Docker build fails with ModuleNotFoundError before the image can be produced. Either let pip resolve bench dependencies or install semantic-version explicitly here.

Useful? React with 👍 / 👎.

Comment thread Dockerfile.layer2
&& curl -fsSL -o /usr/local/lib/docker/cli-plugins/docker-compose \
https://github.com/docker/compose/releases/download/v2.34.0/docker-compose-linux-x86_64 \
&& chmod +x /usr/local/lib/docker/cli-plugins/docker-compose
RUN docker --version && docker compose version

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P1 Badge Install Docker CLI before checking it

When building against the documented dev-bench-base layer, Docker is no longer installed by this Dockerfile before this RUN executes. The previous block downloaded both the Docker client and Compose plugin here, but this change only verifies inherited tools, so builds fail at this layer with docker: not found unless an out-of-repo base image has been rebuilt with Docker already included.

Useful? React with 👍 / 👎.

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.

2 participants