Skip to content

Conversation

@dvdksn
Copy link
Contributor

@dvdksn dvdksn commented Nov 27, 2025

@dvdksn dvdksn added the status/do-not-merge Pull requests that are awaiting some event or decision before they can be merged. label Nov 27, 2025
@github-actions github-actions bot added area/build Relates to Dockerfiles or docker build command area/tests labels Nov 27, 2025
@netlify
Copy link

netlify bot commented Nov 27, 2025

Deploy Preview for docsdocker ready!

Name Link
🔨 Latest commit 2c7b95a
🔍 Latest deploy log https://app.netlify.com/projects/docsdocker/deploys/6979d993f0c31300083b6746
😎 Deploy Preview https://deploy-preview-23782--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.

@dvdksn dvdksn force-pushed the build-input-policy branch from 640026d to b152a76 Compare January 16, 2026 13:38
@github-actions github-actions bot added the area/cli Relates to the CLI client label Jan 16, 2026
@dvdksn dvdksn force-pushed the build-input-policy branch 2 times, most recently from 1dcccf6 to 7741d9b Compare January 20, 2026 14:57
@dvdksn dvdksn requested a review from tonistiigi January 20, 2026 14:59
@dvdksn dvdksn marked this pull request as ready for review January 20, 2026 14:59
@dvdksn dvdksn force-pushed the build-input-policy branch 2 times, most recently from 9ef9e13 to 04835cd Compare January 20, 2026 15:22
@dvdksn dvdksn changed the title [WIP] build: rego source policies build: rego source policies Jan 20, 2026
@dvdksn dvdksn force-pushed the build-input-policy branch from 04835cd to 92feb6f Compare January 20, 2026 15:34
```

When using Sigstore signatures, additional fields are available under
`input.image.signature` (singular) with details about the signing workflow.
Copy link
Member

Choose a reason for hiding this comment

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

?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Uuh I reckon this was a result of me starting to preemptively doc some fields before I was able to test. Then Claude went and mangled things.

}
```

#### `input.git.commitChecksum`
Copy link
Member

Choose a reason for hiding this comment

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

There is also checksum isAnnotatedTag.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Adding these and a couple other fields I noticed were missing. Not adding fullUrl and isSha256 just yet - I noticed they exist but I'm not really able to test those.

@dvdksn dvdksn force-pushed the build-input-policy branch from 92feb6f to 2040f30 Compare January 21, 2026 08:45
@dvdksn dvdksn force-pushed the build-input-policy branch from 2040f30 to d94ec3e Compare January 26, 2026 13:14
@github-actions github-actions bot added dependencies Vendoring, packaging updates area/config labels Jan 26, 2026
@dvdksn dvdksn removed status/do-not-merge Pull requests that are awaiting some event or decision before they can be merged. dependencies Vendoring, packaging updates area/config labels Jan 26, 2026
@dvdksn dvdksn requested a review from a team January 26, 2026 13:14
@dvdksn dvdksn force-pushed the build-input-policy branch from d94ec3e to d803575 Compare January 27, 2026 14:25
@dvdksn dvdksn force-pushed the build-input-policy branch from d803575 to c7656bd Compare January 27, 2026 15:51
$ docker buildx policy test --filename app.Dockerfile .
```

This loads `app.Dockerfile.rego` and runs `*_test.rego` files against it.
Copy link
Contributor

Choose a reason for hiding this comment

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

Same as above. What is the expected outcome? A short sentence might help wrap up what to expect

@usha-mandya
Copy link
Member

Left some minor comments @dvdksn. Looks great overall!

> like `allow if { input.image; print(...) }` only prints for image inputs,
> not for Git repos, HTTP downloads, or local files.

## Common issues
Copy link
Contributor

Choose a reason for hiding this comment

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

What do we think about separating debugging reference from troubleshooting? It doesn't have to be for teh release, but maybe for future work. I think while the two types of info are similar, debugging reads as things a user can do to find an unknown issue whereas troubleshooting are topics that we know are common missteps.

I also might include specific error codes of some kind, or specific error message a user might encounter related to these topics if we have that info readily available. Not a blocker just an idea!

Copy link
Contributor

@akristen akristen left a comment

Choose a reason for hiding this comment

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

These are really informative docs w/ a lot of good details. Some copy level things beyond the general suggestions i left in the PR:

  • Our style guide suggests we use - construction sparingly. I might get a list of all the times you use a - and rework those sentences to use :s, semicolons, commons, whatever you want.
  • Do we always capitalize git? I didn't see anything in our style guide on guidance and I could be wrong... might be handy for me to know, lol.

Overall the one thing I might add to the introduction is more frontloaded context about WHO WHAT WHEN re: creating build policies. Is it something we recommend for larger enterprise orgs? Individual devs? What is the purpose of including these in production or dev: is it better security and compliance, or are there other benefits?

Signed-off-by: David Karlsson <[email protected]>
Copy link
Member

@usha-mandya usha-mandya left a comment

Choose a reason for hiding this comment

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

LGTM

@dvdksn dvdksn merged commit d7d5069 into docker:main Jan 28, 2026
15 checks passed
@dvdksn dvdksn deleted the build-input-policy branch January 28, 2026 09:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/build Relates to Dockerfiles or docker build command area/cli Relates to the CLI client area/tests status/review

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants