Z Open Editor on CodeReady Workspaces

[odrodrig]

I am running CodeReady Workspaces 2.1 on OpenShift 4.3.12 and am trying to install the Z Open Editor according to this article and am getting the following error when starting the workspace:

Error: Failed to run the workspace: "The following containers have terminated:
vscode-zowee0t: reason = 'Error', exit code = 127, message = 'null'"

As of right now, is it even possible to run Z Open Editor on CodeReady Workspaces?

Full log output when starting workspace:

Pulling image "registry.redhat.io/codeready-workspaces/pluginbroker-metadata-rhel8@sha256:6c9abe63a70a6146dc49845f2f7732e3e6e0bcae6a19c3a6557367d6965bc1f8"
Successfully pulled image "registry.redhat.io/codeready-workspaces/pluginbroker-metadata-rhel8@sha256:6c9abe63a70a6146dc49845f2f7732e3e6e0bcae6a19c3a6557367d6965bc1f8"
Created container pluginbroker-metadata-rhel8-6c9abe63a7
Starting plugin metadata broker
Started container pluginbroker-metadata-rhel8-6c9abe63a7
List of plugins and editors to install
- IBM/zopeneditor/latest - Provides COBOL and PL/I language servers as well as tools for IBM Z development.
- IBM/zowe/latest - VS Code extension, powered by Zowe CLI, that streamlines interaction with mainframe data sets, USS files, and jobs.
- eclipse/che-machine-exec-plugin/7.9.3 - Che Plug-in with che-machine-exec service to provide creation terminal or tasks for Eclipse CHE workspace containers.
- eclipse/che-theia/7.9.3 - Eclipse Theia
All plugin metadata has been successfully processed
Pulling image "registry.redhat.io/codeready-workspaces/theia-endpoint-rhel8@sha256:ce46c5c0f76b5a3dfde85ea47c3b447fe69a9bfe39c3359ff0fef61bc356def9"
Successfully pulled image "registry.redhat.io/codeready-workspaces/theia-endpoint-rhel8@sha256:ce46c5c0f76b5a3dfde85ea47c3b447fe69a9bfe39c3359ff0fef61bc356def9"
Created container remote-runtime-injectorfqi
Started container remote-runtime-injectorfqi
Pulling image "registry.redhat.io/codeready-workspaces/pluginbroker-artifacts-rhel8@sha256:5815bab69fc343cbf6dac0fd67dd70a25757fac08689a15e4a762655fa2e8a2c"
Successfully pulled image "registry.redhat.io/codeready-workspaces/pluginbroker-artifacts-rhel8@sha256:5815bab69fc343cbf6dac0fd67dd70a25757fac08689a15e4a762655fa2e8a2c"
Created container pluginbroker-artifacts-rhel8-5815bab69f
Starting plugin artifacts broker
Started container pluginbroker-artifacts-rhel8-5815bab69f
Processing plugin IBM/zopeneditor/latest
  Installing plugin extension 1/1
    Plugin already downloaded
Processing plugin IBM/zowe/latest
  Installing plugin extension 1/1
    Plugin already downloaded
Saving log of installed plugins
All plugin artifacts have been successfully downloaded
Pulling image "registry.redhat.io/codeready-workspaces/jwtproxy-rhel8@sha256:63182dae6377ac01fbebdcb9c6a4435681ea88521cfc6e4222fe3920a3641127"
Successfully pulled image "registry.redhat.io/codeready-workspaces/jwtproxy-rhel8@sha256:63182dae6377ac01fbebdcb9c6a4435681ea88521cfc6e4222fe3920a3641127"
Created container che-jwtproxywubs0zce
Started container che-jwtproxywubs0zce
Container image "quay.io/eclipse/che-java11-gradle:nightly" already present on machine
Created container ibmz
Started container ibmz
Pulling image "docker.io/eclipse/che-remote-plugin-runner-java11:7.3.0"
Successfully pulled image "docker.io/eclipse/che-remote-plugin-runner-java11:7.3.0"
Created container vscode-ibm-zopeneditor6s5
Started container vscode-ibm-zopeneditor6s5
Pulling image "quay.io/eclipse/che-sidecar-node:10-0cb5d78"
Successfully pulled image "quay.io/eclipse/che-sidecar-node:10-0cb5d78"
Created container vscode-zowee0t
Started container vscode-zowee0t
Pulling image "registry.redhat.io/codeready-workspaces/machineexec-rhel8@sha256:24b64b5e258e9bd62cbdbdab24780c4f68112696bfdd98687f5895f542cefd77"
Successfully pulled image "registry.redhat.io/codeready-workspaces/machineexec-rhel8@sha256:24b64b5e258e9bd62cbdbdab24780c4f68112696bfdd98687f5895f542cefd77"
Error: Failed to run the workspace: "The following containers have terminated:
vscode-zowee0t: reason = 'Error', exit code = 127, message = 'null'"

[odrodrig]

I was able to get the workspace started using the devfile that doesn't include zowe. Looks like the issue was just with the zowe container. I will continue testing and close the issue if all else works.

[phaumer]

We definitely have Zowe Explorer working in CodeReady as well. We will try reproducing your specific setup.

[phaumer]

@odrodrig could you try again with our latest updates? Please, reopen if you see more issues.