Skip to content
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

Che Theia devfile v2 does not contain theia container #19301

Closed
sleshchenko opened this issue Mar 16, 2021 · 1 comment · Fixed by eclipse-che/che-plugin-registry#885
Closed
Assignees
Labels
area/plugin-registry kind/bug Outline of a bug - must adhere to the bug report template. severity/blocker Causes system to crash and be non-recoverable or prevents Che developers from working on Che code.

Comments

@sleshchenko
Copy link
Member

sleshchenko commented Mar 16, 2021

Describe the bug

Che Theia devfile v2 does not contain theia container. Today when I used quay.io/eclipse/che-plugin-registry:nightly(quay.io/eclipse/che-plugin-registry@sha256:f0cd1864603d090dc01cfb60f508add74f439547929e2771309e87e2ed223d11) I got the following content with $PLUGIN_REGISTRY/v3/plugins/eclipse/che-theia/next/devfile.yaml:

schemaVersion: 2.1.0
metadata:
  name: theia-ide
commands:
  - id: init-container-command
    apply:
      component: remote-runtime-injector
events:
  preStart:
    - init-container-command
components:
  - name: remote-endpoint
    volume:
      ephemeral: true
  - name: remote-runtime-injector
    container:
      image: 'quay.io/eclipse/che-theia-endpoint-runtime-binary:next'
      env:
        - name: PLUGIN_REMOTE_ENDPOINT_EXECUTABLE
          value: /remote-endpoint/plugin-remote-endpoint
        - name: REMOTE_ENDPOINT_VOLUME_NAME
          value: remote-endpoint
      volumeMounts:
        - name: remote-endpoint
          path: /remote-endpoint
@sleshchenko sleshchenko added kind/bug Outline of a bug - must adhere to the bug report template. severity/blocker Causes system to crash and be non-recoverable or prevents Che developers from working on Che code. area/plugin-registry labels Mar 16, 2021
@sleshchenko
Copy link
Member Author

I've set blocker but I'm not sure if broker DevWorkspace support should really blocks the next release.
It may be caused by eclipse-che/che-plugin-registry#881

benoitf added a commit to benoitf/che-plugin-registry that referenced this issue Mar 17, 2021
…dpoints

fix eclipse-che/che#19301

Change-Id: Ia34ea070f5a8ae8f94cb32b1566d0b4535690b58
Signed-off-by: Florent Benoit <fbenoit@redhat.com>
ericwill pushed a commit to eclipse-che/che-plugin-registry that referenced this issue Mar 17, 2021
…dpoints (#885)

fix eclipse-che/che#19301

Change-Id: Ia34ea070f5a8ae8f94cb32b1566d0b4535690b58
Signed-off-by: Florent Benoit <fbenoit@redhat.com>
@benoitf benoitf self-assigned this Mar 17, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/plugin-registry kind/bug Outline of a bug - must adhere to the bug report template. severity/blocker Causes system to crash and be non-recoverable or prevents Che developers from working on Che code.
Projects
None yet
2 participants