Che-machine-exec
Che Machine Exec is a Golang server that spawns and manages terminal and command processes within Eclipse Che workspaces.
Platform availability
Available on 0 of 10 platforms
- Unraid (not listed)
- TrueNAS (not listed)
- Umbrel (not listed)
- ZimaOS (not listed)
- Proxmox (not listed)
- Helm (not listed)
- Mac (not listed)
- Windows (not listed)
- Linux (not listed)
- Any server (not listed)
Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.
64/100 Good
- Maintained
- 100last commit 19 days ago
- Popular
- 2212 GitHub stars
- Easy to install
- 250 install platforms, install notes, Docker image
- Light to run
- 70750 MB minimum RAM
- Security check
- 80no serious findings, 2 minor, CI, tests, OpenSSF Scorecard 6.7/10
- GitHub stars
- 12
- Open issues
- 22
- Last commit
- 2026-11-02
- Latest release
- 7.6.0
- License
- EPL-2.0
- Activity
- rising
Checked 18 days ago - source: GitHub (eclipse-che/che-machine-exec)
Resources & Compatibility
Minimum requirements: 750 MB RAM, 1 GB disk. ARM (e.g. Raspberry Pi) is not supported.
Checked 54 days ago - source: Docker Hub image tags and published docs
First-install notes
- Start Minikube with the required add-ons Start Minikube (a local Kubernetes cluster) with the ingress and dashboard add-ons and the listed memory, CPU, and disk settings, because Che needs those built-in parts and enough headroom or the dashboard and workspaces can fail to start. source
- Watch for the Running phase before opening After starting a devworkspace, run the get devworkspaces command and wait until the PHASE column says Running, because it first shows Starting while the environment is being built and it will not be usable until it finishes. source
- Check overlay storage if using FUSE If you enable FUSE (a file-sharing method for workspaces), run podman info after starting one and confirm the storage driver is overlay, because a different driver can cause files or permissions to fail inside the workspace. source
- Build container image Build the container image manually with: docker build --no-cache -t eclipse/che-machine-exec -f build/dockerfiles/Dockerfile . source
Fetched 42 days ago - each note links to its source
Variants
Alternatives (12)
- ActiveState Komodo IDE - ActiveState Komodo IDE is a retired, open-source, cross-platform integrated development environment for developers to edit, debug, and mana…
- Apache NetBeans - A free, open-source Integrated Development Environment for software developers.
- GNU Emacs - GNU Emacs is an extensible, customizable text editor—and more.
- Geany - Geany is a powerful, stable and lightweight programmer's text editor that provides tons of useful features without bogging down your workfl…
- Gram - Gram is a powerful and modern source code editor.
- Helix
- IntelliJ IDEA - IntelliJ IDEA is a Java-based integrated development environment (IDE) offering intelligent code completion, refactoring, and debugging too…
- Microsoft Visual Studio - Microsoft Visual Studio is an IDE used to create programs, apps, websites, and web services using various frameworks.
- Neovim - Refactored version of Vim with enhanced extensibility and modern plugin architecture.
- PyCharm - IDE for Python and Django offering refactoring, code analysis, VCS integration, debugger, deployment, and more, with a Community Edition op…
- Qodana Python - Qodana for Python is a quality-monitoring tool that scans your code for errors, security flaws, and inefficiencies.
- VSCodium - VSCodium is a community-driven, freely-licensed binary distribution of Microsoft's VS Code.
Checked 40 days ago - source: AlternativeTo
Common questions
What protocol does che-machine-exec use to communicate with clients?
It uses the JSON-RPC protocol to communicate with the client.
Which Minikube add-ons should be enabled when installing Che?
Start Minikube with the ingress and dashboard add-ons, and provide the listed memory, CPU, and disk settings. Che needs those built-in parts and enough headroom, or the dashboard and workspaces can fail to start.
How can a user know a Che workspace is ready to use?
Run the get devworkspaces command after starting a devworkspace and wait until the PHASE column says Running. It first shows Starting while the environment is being built, so it is not usable until that finishes.
What storage check is needed if FUSE is enabled for Che workspaces?
Run podman info after starting a workspace and confirm the storage driver is overlay. A different driver can cause files or permissions to fail inside the workspace.
What behavior does an open che-machine-exec issue request?
It asks that che-machine-exec not fail with a help log.fatal message. It also asks that critical messages be logged and sent to the client.
Answers sourced from github.com, github.com, github.com, github.com, github.com
Community
Collected 48 days ago - public community threads