Skip to content

fix(ci): use stable ubuntu/bind9 tag to fix container scans - #9

Open
turbobadger wants to merge 1 commit into
mainfrom
fix/container-scan-tags
Open

fix(ci): use stable ubuntu/bind9 tag to fix container scans#9
turbobadger wants to merge 1 commit into
mainfrom
fix/container-scan-tags

Conversation

@turbobadger

Copy link
Copy Markdown
Owner

🔧 Fixes the red X in container security scans

Problem: The ubuntu/bind9:9.18-24.04_edge tag was unstable and causing CI failures

Solution: Switch to the stable LTS tag: ubuntu/bind9:9.18-22.04_lts

Result: Container security scans should now pass ✅

This resolves the recurring red crosses in the CI workflow.

- Replace 9.18-24.04_edge with 9.18-22.04_lts to fix container scan failures
- The edge tag was causing CI failures due to instability
@turbobadger turbobadger self-assigned this Sep 17, 2025
@github-advanced-security

Copy link
Copy Markdown

This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation.

@turbobadger
turbobadger enabled auto-merge (squash) September 17, 2025 07:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants