Skip to content

Commit d6ad97f

Browse files
authored
Update distroless.md (#23259)
`###` should be `##` <!--Delete sections as needed --> ## Description <!-- Tell us what you did and why --> ## Related issues or tickets <!-- Related issues, pull requests, or Jira tickets --> ## Reviews <!-- Notes for reviewers here --> <!-- List applicable reviews (optionally @tag reviewers) --> - [ ] Technical review - [ ] Editorial review - [ ] Product review
1 parent 5da235a commit d6ad97f

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

content/manuals/dhi/core-concepts/distroless.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ Images](../../docker-hub/image-library/trusted-content.md#verified-publisher-ima
1717
follow similar best practices for minimalism and security but may not be as
1818
stripped down to ensure compatibility with a wider range of use cases.
1919

20-
### What are minimal or distroless images?
20+
## What are minimal or distroless images?
2121

2222
Traditional container images include a full OS, often more than what is needed
2323
to run an application. In contrast, minimal or distroless images include only:
@@ -36,7 +36,7 @@ They typically exclude:
3636
Docker Hardened Images are based on this model, ensuring a smaller and more
3737
secure runtime surface.
3838

39-
### What you gain
39+
## What you gain
4040

4141
| Benefit | Description |
4242
|------------------------|-------------------------------------------------------------------------------|
@@ -45,7 +45,7 @@ secure runtime surface.
4545
| Improved security | Lack of shell and package manager limits what attackers can do if compromised |
4646
| Better compliance | Easier to audit and verify, especially with SBOMs and attestations |
4747

48-
### Addressing common tradeoffs
48+
## Addressing common tradeoffs
4949

5050
Minimal and distroless images offer strong security benefits, but they can
5151
change how you work with containers. Docker Hardened Images are designed to
@@ -60,7 +60,7 @@ maintain productivity while enhancing security.
6060
By balancing minimalism with practical tooling, Docker Hardened Images support
6161
modern development workflows without compromising on security or reliability.
6262

63-
### Best practices for using minimal images
63+
## Best practices for using minimal images
6464

6565
- Use multi-stage builds to separate build-time and runtime environments
6666
- Validate image behavior using CI pipelines, not interactive inspection

0 commit comments

Comments
 (0)