🐛 [bug] - argument --allow-insecure-registry does not exist in the cosign tool

[rtaniguchi]

📝 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.

[eformat]

hi @jfilipcz can you please take a look ? seems related to your pr's, cheers

#231

[jfilipcz]

Sure - let me look at that

[jfilipcz]

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 cosign version would be great)

[rtaniguchi]

Hi,

This is the content from the command line execution:
➜ /bin cosign version
______ ______ . __ _______ . .
/ | / __ \ / || | / || \ | |
| ,----'| | | | | (----| | | | __ | \| | | | | | | | \ \ | | | | |_ | | . |
| ----.| --' | .----) | | | | || | | |\ |
_| ______/ |_/ || __| || _|
cosign: A tool for Container Signing, Verification and Storage in an OCI registry.

GitVersion: v1.7.2
GitCommit: 1b1bca3280994eebe38d35e03bbd66af6214f0f1
GitTreeState: clean
BuildDate: 2022-04-12T11:58:39Z
GoVersion: go1.17.8
Compiler: gc
Platform: linux/amd64

If you want to access the class environment, we are using this one:
https://codeready-tl500-workspaces.apps.tl500-bocvt.ls-na.ole.redhat.com/dashboard
You might want to try the environment from the user kdhillon

[jfilipcz]

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.

[alvarolop]

Hello, I think that this Issue is not relevant anymore, I don't see errors during exercise execution, so I recommend closing the issue and we will open it again if necessary