cwctl start fails on keychainless system

[tetchel]

From https://ci.eclipse.org/codewind/job/Codewind/job/codewind-vscode/job/testsInJenkins/47/console
CLI version 2020-03-19-12:11:47

10:41:41  [INFO: 14:41:38.845 CLIWrapper.js:127]: Running CLI command: cwctl --json start -t latest
10:41:41  
10:41:41  [ERRO: 14:41:38.888 CLIWrapper.js:168]: Error running cwctl --json start -t latest
10:41:41  
10:41:41  [ERRO: 14:41:38.888 CLIWrapper.js:170]: Stdout: Debug: false
10:41:41  ==> created file /home/genie.codewind/.codewind/latest/home/genie.codewind/.codewind/docker-compose.yaml
10:41:41  
10:41:41  [ERRO: 14:41:38.888 CLIWrapper.js:176]: Stderr: 2020/03/19 14:41:38 WRITE_FILE_ERROR[204]: {"error":"sec_keyring","error_description":"dbus: invalid bus address (invalid or unsupported transport)"}.
10:41:41  
10:41:41  [DBUG: 14:41:38.889 LocalCodewindManager.js.setState():144]: Local Codewind state changing from Starting to Error starting
10:41:41  
10:41:41  [ERRO: 14:41:38.890 CLILifecycleWrapper.js:194]: Error starting codewind Error running cwctl start: 2020/03/19 14:41:38 WRITE_FILE_ERROR[204]: {"error":"sec_keyring","error_description":"dbus: invalid bus address (invalid or unsupported transport)"}. 

I suspect this is caused by the changes for #1306

[rwalle61]

for cwctl start to use the insecure keychain, we need to do

cwctl --insecure-keyring start

or

export INSECURE_KEYRING=true
cwctl start

Yesterday we updated the PFE Jenkinsfile to do the latter (https://github.com/eclipse/codewind/blob/master/Jenkinsfile#L20), and probably forgot to update the Jenkinsfile for the codewind-installer repo too

[tetchel]

oh, i didn't realize it had to be explicitly enabled. I guess this is the expected behaviour then

[rwalle61]

yep, cwctl uses the secure system keyring by default, unless we tell it to use our insecure one

[jopit]

This change means Codewind 0.11.0 won't start on many Linux systems out of the box, even if the user doesn't need docker registry credentials (i.e. they're not using appsody projects, or are only using public appsody stacks)

Potential fixes

1. Add a preference in the IDEs to enable the insecure registry and document that users should set that preference if they can't start codewind due to this.
2. Add the preference and have the IDE's detect that startup fails due to this issue and offer to set the preference for the user.
3. Cwctl adds a --no-keyring parameter which bypasses the use of the keyring for in PFE, and the IDEs add preferences for both this and the insecure keyring, and when they detect that startup fails due to this issue and offer to set one of these preference for the user.
4. Something else?

[tetchel]

I think 1) and 2) are good, but I'd like it if cwctl could return a better error (and the same error on all platforms) when a keyring is not found or misconfigured so we can look for that specific error.