rht-labs / enablement-codereadyworkspaces Goto Github PK

Workspace fails to start, and this is shown in the log:

2020-03-02 17:41:36,335[/172.30.0.1/...]  [ERROR] [.i.k.KubernetesInternalRuntime 915]  - Unrecoverable event occurred during workspace 'workspace7gxhctl9lz7s84wm' startup: Failed, Failed to pull image "eclipse/che-theia:latest": rpc error: code = Unknown desc = manifest for docker.io/eclipse/che-theia:latest not found, workspace7gxhctl9lz7s84wm.dockerimage-68f5c85f5f-n42jk
2020-03-02 17:41:36,338[aceSharedPool-1]  [WARN ] [.i.k.KubernetesInternalRuntime 243]  - Failed to start Kubernetes runtime of workspace workspace7gxhctl9lz7s84wm. Cause: Unrecoverable event occurred: 'Failed', 'Failed to pull image "eclipse/che-theia:latest": rpc error: code = Unknown desc = manifest for docker.io/eclipse/che-theia:latest not found', 'workspace7gxhctl9lz7s84wm.dockerimage-68f5c85f5f-n42jk'

Workspace should be pulling the Che Theia image from quay.io, not from docker.io.

The Factory URL Link is very handy for creating multiple workspaces by users.

Limit this using ENV variables in CRW deploy (see Che/CRW docs for exact ones)

FROM registry.redhat.io/codeready-workspaces/stacks-node-rhel8

we can use the newer RHEL8 ubi once there is a mongodb for it pulled in the Dockerfile here:

COPY mongodb-org-3.6.repo /etc/yum.repos.d/

Fix CVE's brought in by maven install in Dockerfile. We could use rh-maven package if appropriate

ARG MAVEN_VERSION=3.6.1
ARG MAVEN_URL=https://archive.apache.org/dist/maven/maven-3/$MAVEN_VERSION/binaries/apache-maven-$MAVEN_VERSION-bin.tar.gz

CVE's reposted in quay.io here:

https://quay.io/repository/rht-labs/stacks-node-rhel7-ansible

Also, we could question the need for maven ... ultimately we need java in the image for testing (selenium dependency) but mvn is nice to have ?

currently using default admin password for CRW setup. dont do this.

when using the che Task > Run in excercise 1&2 to clone repos, the terminals do not exit. perhaps add sleep 2 && exit 0; to factory definition.

COPY rhel7.repo /etc/yum.repos.d/

In the Dockerfile that creates the image for the stack, we pull in dependencies from RHEL for chrome headless testing.

When using UBI, These deps should be able to be pulled automatically if the image build is done from a subscribed host (e.g. and openshift node).

When i tried this build in OpenShift, the UBI did not seem to do this though, hence the need for the rhel7.repo definition.

Ultimately the base UBI image in the CRW may be old or need the latest version

FROM registry.redhat.io/codeready-workspaces/stacks-node