Desktop Troubleshooting
Common issues running the BioNodulo desktop app and how to resolve them.
A node fails immediately with “command not found”
The node’s underlying tool isn’t available. Either:
- Install a container runtime (Docker or compatible) so containerized nodes work out of the box, or
- Install the tool natively and ensure it’s on your
PATH.
See First-Run Setup → Container runtime.
A run is killed with an out-of-memory error
The node needed more RAM than your local cap allows. Options:
- Raise the Max RAM limit in Settings → Engine (if your machine has the headroom).
- Run on a smaller input/subset to test the graph.
- Push the heavy step to the cloud.
The app won’t open on macOS (“unidentified developer”)
The build is notarized; on first launch right-click the app → Open to approve it. This prompt appears only once.
Runs are slow
- Increase CPU cores and concurrent nodes in engine settings.
- Make sure your workspace directory is on a fast local disk (not a network mount).
- Reuse cached results: re-running reuses completed nodes via checkpointing, so only changed nodes recompute.
Container runtime not detected
Confirm the runtime is running (docker info succeeds), then restart BioNodulo so
it re-detects the runtime.
Collecting logs for a bug report
Open Help → Open Logs to reveal the log directory. Attach the relevant
run-*.log to a GitHub issue
along with the workflow JSON and your OS/version.
Still stuck?
- Discord for real-time help.
- GitHub Discussions for questions.