-
Notifications
You must be signed in to change notification settings - Fork 40
Clarify project details #61
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.
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure I understand why "images" in this sentence is linked to the "releases" section:
kaniko is meant to be run as an image.
0480c64
to
68104d9
Compare
Because there is no such thing anymore as a static image name .. if uses build container image themselves they can use any name .. if they use chainguard the name will depend on their image and also their account name .. maybe we need a generic placeholder that replaces the old |
- Add History section - Add info about releases as tags only - Add info about binaries from Chainguard and build your own - Update changelog Signed-off-by : Manfred Moser <manfred@simpligility.ca>
…_actions/docker/setup-buildx-action-3.11.0 chore(deps): bump docker/setup-buildx-action from 3.10.0 to 3.11.0
Another look please @cpanato @priyawadhwa |
Description
Signed-off-by : Manfred Moser manfred@simpligility.ca
I think this provides a good base for the project going forward. The following aspects could be discussed as next steps:
gcr.io
as container registry since these binaries are outdated and will no longer be updated.Reviewer Notes