-
Notifications
You must be signed in to change notification settings - Fork 111
Conversation
beab63e
to
6b2e379
Compare
crw-ci-test |
fi \ | ||
fi | ||
# Light image without node. We include remote binary to this image. | ||
FROM alpine |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
hello, please add the version for the image (to be sure to not get unwanted) updates
#invalidate cashe | ||
ADD https://${GITHUB_TOKEN}:x-oauth-basic@api.github.com/repos/theia-ide/theia/git/refs/head /tmp/branch_info.json | ||
ADD https://${GITHUB_TOKEN}:x-oauth-basic@api.github.com/repos/eclipse/che-theia/git/refs/head /tmp/branch_info.json | ||
RUN mkdir /home/theia |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we need this docker image if we do injection of the binary ?
or it's to have the binary for injection that we're making this image ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This image will be init container for Che theia editor plugin.
trap 'responsible_shutdown' SIGHUP SIGTERM SIGINT | ||
|
||
cd ${HOME} | ||
trap 'responsible_shutdown' HUP TERM INT |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is there a reason to change the traps ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, of course, SIGHUP SIGTERM SIGINT doesn't work on fedora.
@@ -22,7 +21,7 @@ export class ChePluginApiProvider implements ExtPluginApiProvider { | |||
initFunction: 'initializeApi', | |||
initVariable: 'che_api_provider' | |||
}, | |||
backendInitPath: path.join(__dirname, '../plugin/node/che-api-node-provider.js') | |||
backendInitPath: '@eclipse-che/theia-plugin-ext/lib/plugin/node/che-api-node-provider.js' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
maybe this change and the next one could be merged in another PR
crw-ci-test |
E2E Happy path tests of Eclipse Che Single User on K8S (minikube v1.1.1) has been successful:
|
Signed-off-by: Oleksandr Andriienko <oandriie@redhat.com>
6b2e379
to
4ba4ebf
Compare
E2E Happy path tests of Eclipse Che Single User on K8S (minikube v1.1.1) has failed:
|
E2E Happy path tests of Eclipse Che Single User on K8S (minikube v1.1.1) has failed:
|
E2E Happy path tests of Eclipse Che Single User on K8S (minikube v1.1.1) has been successful:
|
ci-build-check |
ci-build |
nexe node_modules/@eclipse-che/theia-remote/lib/node/plugin-remote.js -t alpine-x64-10.16.0 -o /plugin-remote-endpoint | ||
|
||
# Light image without node. We include remote binary to this image. | ||
FROM alpine:3.10.2 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
what is the difference of using FROM ALPINE:3.10.2 and using FROM scratch if we don't install anything and that the binary is self-contained ? it's due to musl linking I suppose ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry, @benoitf, Seems, scratch has only latest tag. And this image has not cp
and has not shell(even without sh). Dockerfile RUN
section doesn't work without sh, so I can not install cp. And I think scratch has not any package manager, because it's empty image, so I don't know how to install cp or so on.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok I see.
I might see another problem.
We generate nexe for alpine but if the runtime is not alpine, what is the behavior ?
like using debian, centos, fedora, etc images ?
as we'll copy the bootstrap to another container ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@benoitf I tested with centos, fedora debian and it is works. List tested images was pretty big. You can see this list 99ae354#diff-f7eaf7e082319e42b2dfd26a86ca0736R80 search by from, I commented code, but each image was tested.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok, still strange but if it works.
. "${base_dir}"/../build.include | ||
|
||
init --name:theia-endpoint-runtime-binary "$@" | ||
build |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
very minor: missing EOF
|
||
USER root | ||
|
||
RUN cd /home/theia && \ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it seems usually linters want that we use WORKDIR /home/theia before but I haven't run linter there so maybe it's fine
|
||
FROM ${BUILD_ORGANIZATION}/${BUILD_PREFIX}-theia:${BUILD_TAG} as builder | ||
|
||
USER root |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
do we need to be root ?
AFAIK we can install stuff globally in theia images ?
Signed-off-by: Oleksandr Andriienko <oandriie@redhat.com>
E2E Happy path tests of Eclipse Che Single User on K8S (minikube v1.1.1) has failed:
|
hello, how to test ? |
All stuff I tested on the minishift. Build che-theia and theia-endpoint-runtime-binary imagesYou need to build che-theia, and theia-endpoint-runtime-binary images, so from my branch:
You can retag and push images to the dockerhub. Use image with upgraded che-plugin-brokerFor integration image theia-endpoint-runtime-binary like init-container for che-theia, you need to use upgraded che-plugin-broker: eclipse-che/che-plugin-broker#75 . You can use mine image: To activate this plugin-broker image in the che, you need to open deployment che-server and apply env variable: CHE_WORKSPACE_PLUGIN__BROKER_UNIFIED_IMAGE aandrienko/che-unified-plugin-broker:latest Redeploy che. Test devfileAnd you can use some test devfile with your che-theia and theia-endpoint-runtime-binary images. Example of mine devfile: https://gist.github.com/AndrienkoAleksandr/ec1efffcbb4b25d52c22029bb7b6ac69 Interesting part of the test devfile.We are using our builded image with che-theia: Init container section here with theia-endpoint-runtime-binary: Sidecar image for typescript lspAnd we need image for sidecar container, here is I used fedora:30: DockerFile In the devfile sidecar plugin here: |
yes |
ci-build |
crw-ci-test |
1 similar comment
crw-ci-test |
E2E Happy path tests of Eclipse Che Single User on K8S (minikube v1.1.1) has failed:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM Tested on che.osio and worked fine. I kind of agree on @benoitf comments but these are things that can be addressed in the later.
E2E Happy path tests of Eclipse Che Single User on K8S (minikube v1.1.1) has failed:
|
E2E Happy path tests of Eclipse Che Single User on K8S (minikube v1.1.1) has failed:
|
The PR was checked manually. All steps in the HappyPath test were passed. |
What does this PR do?
Add image with remote-plugin-endpoint binary
What issues does this PR fix or reference?
eclipse-che/che#13387