Skip to content

dhi guides: securing a backstage portal using DHI#24359

Merged
craig-osterhout merged 12 commits intodocker:mainfrom
ajeetraina:askguide/backstage
Mar 17, 2026
Merged

dhi guides: securing a backstage portal using DHI#24359
craig-osterhout merged 12 commits intodocker:mainfrom
ajeetraina:askguide/backstage

Conversation

@ajeetraina
Copy link
Contributor

Description

This PR adds a guide that shows how to secure a Backstage developer portal container using Docker Hardened Images, covering native module compilation, multi-stage builds, Socket Firewall protection, and distroless runtime images

Related issues or tickets

Reviews

  • Technical review
  • Editorial review
  • Product review

@ajeetraina ajeetraina marked this pull request as ready for review March 13, 2026 09:48
@netlify
Copy link

netlify bot commented Mar 13, 2026

Deploy Preview for docsdocker ready!

Name Link
🔨 Latest commit 5ab9ab1
🔍 Latest deploy log https://app.netlify.com/projects/docsdocker/deploys/69b91450ab3ba90008fd59ad
😎 Deploy Preview https://deploy-preview-24359--docsdocker.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@ajeetraina ajeetraina changed the title user guide: backstage dhi guides: securing a backstage portal using DHI Mar 13, 2026
@usha-mandya
Copy link
Member

/review

Copy link
Contributor

@docker-agent docker-agent bot left a comment

Choose a reason for hiding this comment

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

Review Summary

Assessment: 🟡 NEEDS ATTENTION

This is a comprehensive and well-structured guide for securing Backstage with Docker Hardened Images. The technical content is accurate and the guide demonstrates strong knowledge of multi-stage builds, native module compilation, and DHI customizations.

However, there are several style guide violations that should be addressed:

Critical Issues (2):

  • Hedge word "making it easy" violates the style guide's prohibition on marketing language
  • Time-relative language "soon" should be removed or replaced with specific information

Notable Issues (4):

  • SEO description exceeds the recommended 150-160 character limit (177 chars)
  • Content contradiction: The Important callout says not to add language runtimes as system packages, but the example immediately adds Python as a system package
  • Meta-commentary "This is expected" should be stated directly

Findings

See inline comments for specific recommendations.

Copy link
Contributor

@craig-osterhout craig-osterhout left a comment

Choose a reason for hiding this comment

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

LGTM.
Left some non-blocking nits.

@ajeetraina
Copy link
Contributor Author

@craig-osterhout I have made all the necessary changes. Pls do check it once.

@craig-osterhout craig-osterhout merged commit 8c5bfcc into docker:main Mar 17, 2026
19 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants