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-machine-exec image does not work properly #22917

Open
stringang opened this issue Apr 11, 2024 · 4 comments
Open

che-machine-exec image does not work properly #22917

stringang opened this issue Apr 11, 2024 · 4 comments
Labels
area/machine-exec kind/bug Outline of a bug - must adhere to the bug report template. status/analyzing An issue has been proposed and it is currently being analyzed for effort and implementation approach

Comments

@stringang
Copy link

Describe the bug

when using the devworkspacetemplate resource to create a workspace, the che-machine-exec image(quay.io/eclipse/che-machine-exec:7.84.0) cannot be started.

error message:

exec /go/bin/che-machine-exec: no such file or directory

Che version

7.84@latest

Steps to reproduce

  1. Create the devworkspacetemplate resource(che-machine-exec)
  2. Create workspace resources

Expected behavior

che-machine-exec container runs normally

Runtime

Kubernetes (vanilla)

Screenshots

No response

Installation method

other (please specify in additional context)

Environment

Linux

Eclipse Che Logs

No response

Additional context

No response

@stringang stringang added the kind/bug Outline of a bug - must adhere to the bug report template. label Apr 11, 2024
@tolusha
Copy link
Contributor

tolusha commented Apr 11, 2024

@stringang
Could you share the devfile ?

@stringang
Copy link
Author

@tolusha

apiVersion: workspace.devfile.io/v1alpha2
kind: DevWorkspaceTemplate
metadata:
  annotations:
    controller.devfile.io/allow-import-from: '*'
  name: web-terminal-exec
  namespace: openshift-operators
  labels:
    console.openshift.io/terminal: 'true'
spec:
  components:
    - container:
        cpuRequest: 100m
        command:
          - /go/bin/che-machine-exec
          - '--authenticated-user-id'
          - $(DEVWORKSPACE_CREATOR)
          - '--idle-timeout'
          - $(WEB_TERMINAL_IDLE_TIMEOUT)
          - '--pod-selector'
          - controller.devfile.io/devworkspace_id=$(DEVWORKSPACE_ID)
          - '--use-bearer-token'
        env:
          - name: WEB_TERMINAL_IDLE_TIMEOUT
            value: 15m
        memoryRequest: 128Mi
        sourceMapping: /projects
        cpuLimit: 400m
        memoryLimit: 128Mi
        image: 'quay.io/eclipse/che-machine-exec:7.84.0'
        endpoints:
          - attributes:
              type: main
            exposure: public
            name: exec
            protocol: http
            targetPort: 4444
        mountSources: false
      name: web-terminal-exec

---
apiVersion: workspace.devfile.io/v1alpha2
kind: DevWorkspaceTemplate
metadata:
  annotations:
    controller.devfile.io/allow-import-from: '*'
  name: web-terminal-tooling
  namespace: openshift-operators
  labels:
    console.openshift.io/terminal: 'true'
spec:
  components:
    - container:
        args:
          - tail
          - '-f'
          - /dev/null
        cpuLimit: 400m
        cpuRequest: 100m
        image: 'quay.io/wto/web-terminal-tooling:latest'
        memoryLimit: 512Mi
        memoryRequest: 128Mi
        mountSources: false
        sourceMapping: /projects
      name: web-terminal-tooling

@tolusha
Copy link
Contributor

tolusha commented Apr 15, 2024

I assume some libraries are missed in the container to run a go binary.
I don't if it is used currently anywhere.
It would be nice to have contribution into the project [1]
[1] https://github.com/eclipse-che/che-machine-exec/blob/main/build/dockerfiles/Dockerfile

@ibuziuk ibuziuk added area/machine-exec status/analyzing An issue has been proposed and it is currently being analyzed for effort and implementation approach labels Apr 15, 2024
@stringang
Copy link
Author

stringang commented Apr 17, 2024

the root cause is enable CGO_ENABLED compilation

It was this PR change that caused: eclipse-che/che-machine-exec#258

The problem can also be reproduced by running with docker:

docker run quay.io/eclipse/che-machine-exec:7.84.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/machine-exec kind/bug Outline of a bug - must adhere to the bug report template. status/analyzing An issue has been proposed and it is currently being analyzed for effort and implementation approach
Projects
None yet
Development

No branches or pull requests

3 participants