# Helpful utilities

2 min read

---

Handy scripts and shell snippets to make your life easier when working with Edera. Nothing fancy—just stuff that works.

## Apply the Edera RuntimeClass [Permalink for this section](https://docs.edera.dev/support/troubleshooting/utilities/#apply-the-edera-runtimeclass)

```bash
kubectl apply -f https://public.edera.dev/kubernetes/runtime-class.yaml
```

**Note:** The Edera RuntimeClass requires nodes to be labeled with `runtime=edera`. See the [installation guides](https://docs.edera.dev/guides/install/) for labeling instructions.

## Quick check: are all of the Edera daemons active? [Permalink for this section](https://docs.edera.dev/support/troubleshooting/utilities/#quick-check-are-all-of-the-edera-daemons-active)

On your node run:

```bash
systemctl list-units --type=service | grep protect
```

Expected outcome:

```bash
protect-cri.service                    loaded active running Edera Protect CRI
protect-daemon.service                 loaded active running Edera Protect Daemon
protect-network.service                loaded active running Edera Protect Networking Daemon
protect-preinit.service                loaded active exited  Edera Protect Pre-Initialization
protect-storage.service                loaded active running Edera Protect Storage Daemon
```

## SSH into a Tailscale node [Permalink for this section](https://docs.edera.dev/support/troubleshooting/utilities/#ssh-into-a-tailscale-node)

This is a helpful script if you are using Tailscale to ssh

```bash
dera_tailscale_ssh_to_node() {
  NODE_NAME=$(kubectl get nodes --no-headers | awk '{print $1}' | cut -d'.' -f1)
  if [[ -n "$NODE_NAME" ]]; then
    ssh root@"$NODE_NAME"
  else
    echo "No nodes found or unable to extract the node name."
  fi
}
```

## Check Edera version and build info [Permalink for this section](https://docs.edera.dev/support/troubleshooting/utilities/#check-edera-version-and-build-info)

Starting in v1.6.0, all Edera binaries report their build SHA for easier debugging and support:

```bash
protect --version
```

Example output:

```bash
edera-protect-ctl 1.6.0+sha.v1.6.0
```

The format is `<version>+sha.<commit>`. When reporting issues, include this full version string.

## Validate system readiness with edera-check [Permalink for this section](https://docs.edera.dev/support/troubleshooting/utilities/#validate-system-readiness-with-edera-check)

[`edera-check`](https://docs.edera.dev/reference/edera-check/) is a standalone tool that validates your system before or after installing Edera. It checks hardware requirements, kernel configuration, and captures a diagnostic bundle.

**Before installing:**

```bash
docker run --pull always --pid host --privileged \
  ghcr.io/edera-dev/edera-check:stable preinstall
```

**After installing:**

```bash
docker run --pull always --pid host --privileged \
  ghcr.io/edera-dev/edera-check:stable postinstall
```

The report bundle it generates is useful when contacting [support@edera.dev](mailto:support@edera.dev). See the [full reference](https://docs.edera.dev/reference/edera-check/) for details.

## More tools coming soon [Permalink for this section](https://docs.edera.dev/support/troubleshooting/utilities/#more-tools-coming-soon)

We’re collecting common tools and scripts here. Have one to contribute? [Let us know](https://docs.edera.dev/support/troubleshooting/utilities/support@edera.dev).

Last updated on 2026-06-09

We use analytics to understand how people use our docs. No personal data is collected.