Rework che-theia remote plugin images
See original GitHub issueThis is sub task of #13387
To complete #13387 we need to rewrite current, alpine based, images. And also provide new optional UBI based images for each of remote plugin. Name of the UBI based docker file will be: Dockerfile.ubi
All work on rewriting images are doing in https://github.com/eclipse/che-theia/tree/reworkImages branch
Current state:
Image name | Current(Alpine) | RHCC based | Rewriter | Req CRW 2 | Req CRW 2+ |
---|---|---|---|---|---|
eclipse/che-remote-plugin-runner-java8 | β | β | β | ||
eclipse/che-remote-plugin-runner-java11 | β | β | β | ||
eclipse/che-remote-plugin-php7 | β | β | Oleksandr | β | |
eclipse/che-remote-plugin-go-1.10.7 | β | β | |||
eclipse/che-remote-plugin-go-1.11.5 | β | β | (RHCC has 1.11.5) | β | |
eclipse/che-remote-plugin-go-1.12.9 | β | β | Oleksandr | ||
eclipse/che-remote-plugin-clang-8 | β | β | β | ||
eclipse/che-remote-plugin-python-3.7.3 | β | β | |||
eclipse/che-remote-plugin-python-3.7.4 | β | β | β | ||
eclipse/che-remote-plugin-dotnet-2.1.509 | β | β | (RHCC has 2.1.509) | β | |
eclipse/che-remote-plugin-dotnet-2.2.105 | β | β | |||
eclipse/che-remote-plugin-kubernetes-tooling-0.1.17 | β | β | |||
eclipse/che-remote-plugin-kubernetes-tooling-1.0.0 | β | β | β | ||
eclipse/che-remote-plugin-kubernetes-tooling-1.0.4 | ? | ? | ? | ||
eclipse/che-remote-plugin-openshift-connector-0.0.17 | β | β | |||
eclipse/che-remote-plugin-openshift-connector-0.0.21 | β | β | |||
eclipse/che-remote-plugin-openshift-connector-0.1.0 | β | β | β | ||
eclipse/che-remote-plugin-dependency-analytics-0.0.12 | β | β | |||
eclipse/che-remote-plugin-dependency-analytics-0.0.13 | β | β | β | ||
eclipse/che-remote-node(new for typescript) | β | β | @AndrienkoAleksandr | β | |
eclipse/che-remote-plugin-camelk-0.0.9 | β | β |
Issue Analytics
- State:
- Created 4 years ago
- Comments:15 (15 by maintainers)
Top Results From Across the Web
eclipse/che-remote-plugin-runner-java8:7.1.0 | Docker Hub
Image. Image Layers. 1. ADD file ... in /. 2.63 MB. 2. CMD ["/bin/sh"] ... /bin/sh -c rm -rf /home/theia/node_modules/@eclipse-che/theia-plugin-ext.
Read more >Chapter 2. Che-Theia IDE basics - Red Hat Customer Portal
To configure Git identity using the command line, open the terminal of the Che-Theia container. Navigate to the My Workspace view, and open...
Read more >How to build Che Theia image with my own changes?
The sources of eclipse/che-theia is located here. After the changes are made, you need to rebuild the image with the following command:Β ...
Read more >Eclipse Che 7: New & Noteworthy
export function update(workspaceId: string, workspace: cheApi.workspace. ... image: "docker.io/eclipse/che-remote-plugin-runner-java11:next".
Read more >Move your VS Code extension into Eclipse Che
image : quay.io/eclipse/che-python-3.7:nightly ... VSCode extension with custom plugin registry ... Using nexe tool on Eclipse Che Theia remote package.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Ah, I see the WIP is in https://github.com/eclipse/che-theia/tree/reworkImages/dockerfiles/ rather than master branch.
I also see that weβre not following the existing convention of using
rhel.Dockerfile
or Dockerfile.rhel, but have created another convention for Dockerfile.rh.Can I suggest refactoring those to
rhel.Dockerfile
for two reasons?a) consistency with other builds like the plugin/devfile registries b) using .Dockerfile suffix means you can get linting and code completion in VSCode automatically.
@benoitf WDYT?
We are done with this issue.