Skip to content

[Snyk] Security upgrade caddy from 2.10.2-alpine to 2.11-alpine#209

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

Open
codingdud wants to merge 1 commit into
base:main
Choose a base branch
from
Open

[Snyk] Security upgrade caddy from 2.10.2-alpine to 2.11-alpine #209

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 frontend/Dockerfile.production
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -28,7 +28,7 @@ RUN npm run build

#CMD serve -s build

FROM caddy:2.10.2-alpine
FROM caddy:2.11-alpine

@gemini-code-assistgemini-code-assistBotJan 10, 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.

medium

While upgrading for security is important, this change replaces a specific patch version tag (2.10.2-alpine) with a floating minor version tag (2.11-alpine). For production Dockerfiles, it's a best practice to pin base images to a specific patch version (e.g., 2.11.0-alpine) or an image digest (@sha256:...). This ensures build reproducibility and prevents unexpected changes from being pulled in automatically.

FROM caddy:2.11.0-alpine
References
  1. Pin Docker base images to a specific version or digest in production to ensure reproducible builds.



ARG CERT
Expand Down