Skip to content

build(deps): bump the infra-base-images group across 2 directories with 4 updates #286

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
dependabot wants to merge 1 commit into from
Closed

build(deps): bump the infra-base-images group across 2 directories with 4 updates #286

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion src/agent_env/env/envs/service_db/Dockerfile
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
FROM public.ecr.aws/docker/library/postgres:16-alpine@sha256:721873c34ceb9f8d8fc265984940dc982404c105f19ad51be9fdc5970a6080ea
FROM public.ecr.aws/docker/library/postgres:18-alpine@sha256:77f585114c32fbca283dc835b0596f4e52b51b4c6662d7810b2f4084f60a1873

@greptile-apps greptile-apps Bot Oct 21, 2026

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 Database snapshots stop working

PostgreSQL 18 uses /var/lib/postgresql/18/docker as its default PGDATA, but _snapshot_servicedb still copies /var/lib/postgresql/data. Snapshot creation therefore cannot export the database.

That function also builds snapshots on PostgreSQL 16, which cannot read PostgreSQL 18 data files even after the copy path is fixed. Update snapshot capture and its base image together, or retain PostgreSQL 16.

Prompt To Fix With AI 
This is a comment left during a code review.
Path: src/agent_env/env/envs/service_db/Dockerfile
Line: 1

Comment:
**Database snapshots stop working**

PostgreSQL 18 uses `/var/lib/postgresql/18/docker` as its default `PGDATA`, but `_snapshot_servicedb` still copies `/var/lib/postgresql/data`. Snapshot creation therefore cannot export the database.

That function also builds snapshots on PostgreSQL 16, which cannot read PostgreSQL 18 data files even after the copy path is fixed. Update snapshot capture and its base image together, or retain PostgreSQL 16.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

Fix in Cursor Fix in Claude Code Fix in Codex


# ServiceDBEnv - PostgreSQL database for MCP services
#
Expand Down
2 changes: 1 addition & 1 deletion src/agent_env/env/envs/service_db/Dockerfile.db-mcp
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,7 +24,7 @@ RUN sed -i 's/mcp = FastMCP("postgres-mcp")/from mcp.server.transport_security i

RUN uv sync --frozen --no-dev

FROM public.ecr.aws/docker/library/python:3.12-slim-bookworm@sha256:6a0e06f5ba0b373d051aabd3fffb9b873f27f9a2a3a14bcbe37dee6f0e3bbc70
FROM public.ecr.aws/docker/library/python:3.15-slim-bookworm@sha256:0e019bbdfb5d9874cb2389f1c2884b64aa2ac97c99960b5bc521cef978c0617d

@greptile-apps greptile-apps Bot Oct 21, 2026

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 Database tools cannot start

Dockerfile.db-mcp still builds /app/.venv with Python 3.12, but now copies it into a Python 3.15 image. The copied environment depends on the builder's Python 3.12 interpreter and packages. Copying /app does not install that interpreter in the final image, so postgres-mcp cannot start.

Keep both stages on the same Python version, or rebuild the environment for the new runtime.

Prompt To Fix With AI 
This is a comment left during a code review.
Path: src/agent_env/env/envs/service_db/Dockerfile.db-mcp
Line: 27

Comment:
**Database tools cannot start**

`Dockerfile.db-mcp` still builds `/app/.venv` with Python 3.12, but now copies it into a Python 3.15 image. The copied environment depends on the builder's Python 3.12 interpreter and packages. Copying `/app` does not install that interpreter in the final image, so `postgres-mcp` cannot start.

Keep both stages on the same Python version, or rebuild the environment for the new runtime.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

Fix in Cursor Fix in Claude Code Fix in Codex

RUN groupadd -r app && useradd -r -g app app
COPY --from=builder --chown=app:app /app /app

Expand Down
2 changes: 1 addition & 1 deletion src/agent_env/env/envs/service_db/Dockerfile.db-web
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,4 +4,4 @@
# digest) with no anonymous rate limit and no auth required. The digest matches docker.io/sosedoff/pgweb:0.16.2. To bump: pick a
# new tag from https://github.com/sosedoff/pgweb/pkgs/container/pgweb and update
# the tag + digest here.
FROM ghcr.io/sosedoff/pgweb:0.16.2@sha256:8f1ed22e10c9da0912169b98b62ddc54930dc39a5ae07b0f1354d2a93d44c6ed
FROM ghcr.io/sosedoff/pgweb:0.17.0@sha256:a5256d416e2e8b92d69a4459058e3eca33a9f075d8325491644411d0bc3bd70b
2 changes: 1 addition & 1 deletion src/agent_env/env/envs/website_browser/Dockerfile
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
FROM public.ecr.aws/docker/library/node:22-slim@sha256:813a7480f28fdadac1f7f5c824bcdad435b5bc1322a5968bbbdef8d058f9dff4
FROM public.ecr.aws/docker/library/node:26-slim@sha256:36793bcbb160a6a16cede1e62b93f84e26b78a972a8a4c0b879c1c12f22761ec

# Chromium runtime dependencies for headless mode, and python3 for the socket probe the gateway's compose
# health-checks every MCP server with.
Expand Down
Loading