Skip to content

installation: downloads: docker: add v5.1.4 and v5.1.5 tags #2795

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

Merged
eschabell merged 1 commit into from
Oct 24, 2026
Merged

installation: downloads: docker: add v5.1.4 and v5.1.5 tags #2795

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
6 changes: 5 additions & 1 deletion installation/downloads/docker.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -42,6 +42,10 @@ The following table describes the Linux container tags that are available on Doc

| Tags | Manifest Architectures | Description |
| ------------ | ------------------------- | -------------------------------------------------------------- |
| 5.1.5-debug | amd64, arm64, arm/v7 | Debug images |
| 5.1.5 | amd64, arm64, arm/v7 | Release [v5.1.5](https://fluentbit.io/announcements/v5.1.5/) |
Comment thread
eschabell marked this conversation as resolved.
| 5.1.4-debug | amd64, arm64, arm/v7 | Debug images |
| 5.1.4 | amd64, arm64, arm/v7 | Release [v5.1.4](https://fluentbit.io/announcements/v5.1.4/) |
| 5.1.3-debug | amd64, arm64, arm/v7 | Debug images |
| 5.1.3 | amd64, arm64, arm/v7 | Release [v5.1.3](https://fluentbit.io/announcements/v5.1.3/) |
| 5.1.2-debug | amd64, arm64, arm/v7 | Debug images |
Expand Down Expand Up @@ -329,7 +333,7 @@ The reasons for using distroless are well covered in
With any choice, there are downsides:

- No shell or package manager to update or add things.
- Generally, dynamic updating is a bad idea in containers as the time it's done affects the outcome: two containers started at different times using the same base image can perform differently or get different dependencies.
- Generally, dynamic updating is a bad idea in containers as the time it's done affects the outcome. Two containers started at different times using the same base image can perform differently or get different dependencies.
- A better approach is to rebuild a new image version. You can do this with Distroless, but it's harder and requires multistage builds or similar to provide the new dependencies.
- Debugging can be harder.
- More specifically you need applications set up to properly expose information for debugging rather than rely on traditional debug approaches of connecting to processes or dumping memory. This can be an upfront cost versus a runtime cost but does shift left in the development process so hopefully is a reduction overall.
Expand Down
Loading