Skip to content

[CI][Github] Add Fully Qualified Container Names to Best Practices #165067

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
merged 1 commit into from
Oct 25, 2025
Merged

[CI][Github] Add Fully Qualified Container Names to Best Practices #165067

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
17 changes: 17 additions & 0 deletions llvm/docs/CIBestPractices.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -136,3 +136,20 @@ branches as follows:
branches:
- main
- releases/*

Container Best Practices
========================

This section contains best practices/guidelines when working with containers
for LLVM infrastructure.

Using Fully Qualified Container Names
-------------------------------------

When referencing container images from a registry, such as in Github Actions
workflows, or in ``Dockerfile`` files used for building images, prefer fully
qualified names (i.e., including the registry domain) over just the image.
For example, prefer ``docker.io/ubuntu:24.04`` over ``ubuntu:24.04``. This
ensures portability across systems where a different default registry might
be specified and also prevents attackers from changing the default registry
to pull in a malicious image instead of the intended one.
Loading