-
Notifications
You must be signed in to change notification settings - Fork 78
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
🐛 [bug] - argument --allow-insecure-registry does not exist in the cosign tool #242
Comments
Sure - let me look at that |
Hey @rtaniguchi , I suspect the problem was related to version of cosign you had included in the stack image - with the latest version that's being out that should be cleared. One way or another, confirmation of cosign version you have would be great (output of |
Hi, This is the content from the command line execution: GitVersion: v1.7.2 If you want to access the class environment, we are using this one: |
Thanks @rtaniguchi , in the mean time I went through the exercises on my end - the #243 should fix the issue - have a look at the updated instructions. |
📝 Description
... of the issue you're seeing in the content / tech exercise
In the Exercise 3, the image signing activity (https://github.com/rht-labs/tech-exercise/raw/main/docs/3-revenge-of-the-automated-testing/8a-jenkins.md and https://github.com/rht-labs/tech-exercise/blob/main/docs/3-revenge-of-the-automated-testing/8b-tekton.md) the --allow insecure-registry flag in the cosign command is not a valid argument.
🚶 Steps to reproduce
... if applicable
-- Run the command cosign command suggested in the lab
🧙♀️ Suggested solution
... if applicable
Remove the --allow-insecure-registry flag from cosign command.
The text was updated successfully, but these errors were encountered: