---
title: "Uninstalling a Runner"
slug: "uninstalling-a-runner"
description: "Learn how to safely uninstall Traceable runners based on the deployment method. Follow clear steps to remove runners installed via CLI, systemd, Helm, or AWS ECS without leaving residual services."
updated: 2025-12-23T09:52:52Z
published: 2025-12-23T09:52:52Z
---

> ## Documentation Index
> Fetch the complete documentation index at: https://traceabledocs.document360.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Uninstalling a Runner

Uninstalling a runner depends on how the runner was originally deployed. The following tabs highlight the steps to ensure that runners are successfully uninstalled from your environment without leaving residual services or configurations.

> [!NOTE]
> Note
> 
> A deleted runner cannot be restored.

Installed using `install.sh`Installed using Helm chartInstalled on AWS ECS

#### Option 1 - As a `systemd` service

Complete the following steps:

1. Specify the following command to stop the service if it is currently running:

```bash
sudo systemctl stop traceable-runner.service
```
2. Specify the following command to check the status of the service:

```bash
sudo systemctl status traceable-runner.service
```

The above command and recent log entries show whether the service is active, inactive, or has failed.
3. Specify the following command to disable the service:

```bash
sudo systemctl disable traceable-runner.service
```

The above command prevents the service from starting automatically at boot time.
4. Specify the following command to remove the service unit file from your custom location:

```bash
sudo rm /etc/systemd/system/traceable-runner.service
```

The above command removes the file from the `/etc/systemd/system` directory. This directory usually contains the `systemd` service files created or customized by the system administrator.
5. Specify the following command to remove the service unit file from the standard location:

```bash
sudo rm /user/lib/systemd/system/traceable-runner.service
```

The above command removes the file from the `/user/lib/systemd/system/` directory. This directory usually contains `systemd` service files provided by installation packages.
6. Specify the following command to reload the `systemd` manager configuration:

```bash
sudo systemctl daemon-reload
```

The above command reloads the manager configuration. You must run this command to ensure that `systemd` is aware of the above steps.

#### Option 2 - Not as a service

Complete the following steps:

1. Specify the following command to stop the runner:

```bash
traceable runner stop <runner_name>
```
2. Ensure that the Traceable runner process is currently not running:

```bash
ps -ef | grep traceable
```
3. Specify the following command to remove the Traceable CLI installation:

```bash
delete $HOME/.local/traceable directory
```

Enter the following command to uninstall the runner:

```bash
helm uninstall <deployment_name>
```

Complete the following steps:

1. Open your web browser and log in to the AWS management console.
2. In the console, navigate to the **Amazon Elastic Container** Service.
3. Click the cluster where you installed the runner.
4. Delete the runner service.

## Related

- [Runners and CLI](/runners.md)
- [Software and Hardware Requirements](/software-and-hardware-requirements.md)
- [Installing a Runner](/installing-a-runner.md)
- [Understanding Runners Dashboard](/understanding-runner-dashboard.md)