Switching Netdata Install Types and Release Channels

You can switch between different Netdata installation types and release channels based on your needs. This guide covers both scenarios with step-by-step instructions.

Switching Install Types

Data Backups When Switching Install Types

Before switching install types, you need to back up your configuration and data to preserve your settings.

For Native Packages and Local Builds

When backing up configuration and data for install types other than static builds or Docker containers, you should back up these directories:

• /etc/netdata (excluding /etc/netdata/.environment and /etc/netdata/.install-type)
• /var/cache/netdata
• /var/lib/netdata

warning

You must exclude the .environment and .install-type files from your backup. Copying these files from one install type to another will break updates.

For Docker Containers

When backing up configuration and data for Docker containers, you should back up these paths from inside the container:

• /etc/netdata (excluding /etc/netdata/.environment and /etc/netdata/.install-type)
• /var/cache/netdata
• /var/lib/netdata

warning

You must exclude the .environment and .install-type files from your backup. Copying these files from one install type to another will break updates.

For Static Builds

When backing up configuration and data for static builds, you should back up these directories:

• /opt/netdata/etc/netdata (excluding /opt/netdata/etc/netdata/.environment and /opt/netdata/etc/netdata/.install-type)
• /opt/netdata/var/cache/netdata
• /opt/netdata/var/lib/netdata

warning

You must exclude the .environment and .install-type files from your backup. Copying these files from one install type to another will break updates.

Switching Between Install Types (Non-Docker)

For all install types other than Docker images, you can use this officially supported method:

1. Back up your configuration and data that you want to preserve using the appropriate method above.

2. Run the kickstart script with clean reinstall:

   wget -O /tmp/netdata-kickstart.sh https://get.netdata.cloud/kickstart.sh
   sh /tmp/netdata-kickstart.sh --reinstall-clean [OPTIONS_FOR_DESIRED_INSTALL_TYPE]

3. Restore your backups to the appropriate paths in the new installation.

Switching From Native/Static/Local to Docker

To switch from a native, static, or local install to a Docker image:

1. Back up your configuration and data that you want to preserve.

2. Uninstall the existing installation:

   wget -O /tmp/netdata-kickstart.sh https://get.netdata.cloud/kickstart.sh
   sh /tmp/netdata-kickstart.sh --uninstall

3. Start the Docker container for the Netdata agent.

4. Restore your backup contents to the respective paths inside the Docker container (the paths within the container are the same as those used for a native package install on the host).

5. Restart the Docker container to apply the restored configuration.

Switching From Docker to Native/Static/Local

To switch from a Docker container to a different install type:

1. Back up your configuration and data that you want to preserve from inside the container.

2. Remove the container.

3. Install Netdata using the kickstart script:

   wget -O /tmp/netdata-kickstart.sh https://get.netdata.cloud/kickstart.sh
   sh /tmp/netdata-kickstart.sh [OPTIONS_FOR_DESIRED_INSTALL_TYPE]

4. Restore your backups to the appropriate paths in the new installation.

Switching Between Release Channels

Static Builds and Local Builds

For static builds and local builds, you can simply run the kickstart script with the reinstall option:

Switch to Stable Channel

wget -O /tmp/netdata-kickstart.sh https://get.netdata.cloud/kickstart.sh
sh /tmp/netdata-kickstart.sh --reinstall --stable-channel

Switch to Nightly Channel

wget -O /tmp/netdata-kickstart.sh https://get.netdata.cloud/kickstart.sh
sh /tmp/netdata-kickstart.sh --reinstall --nightly-channel

Docker Containers

Follow the standard container recreation process used for updates, but replace the image tag with the one corresponding to your target release channel:

• Stable: Use the stable tag
• Nightly: Use the latest tag

Native Packages

Debian/Ubuntu

Switch from Nightly to Stable

# Install stable repository (automatically removes nightly repo)
sudo apt install netdata-repo
sudo apt update
sudo apt remove netdata
sudo apt install netdata

Switch from Stable to Nightly

# Install nightly repository (automatically removes stable repo)
sudo apt install netdata-repo-edge
sudo apt update
sudo apt remove netdata
sudo apt install netdata

Fedora/RHEL

Switch from Nightly to Stable

# Install stable repository (automatically removes nightly repo)
sudo dnf install --allowerasing netdata-repo
sudo dnf remove netdata
sudo dnf install --refresh netdata

Switch from Stable to Nightly

# Install nightly repository (automatically removes stable repo)
sudo dnf install --allowerasing netdata-repo-edge
sudo dnf remove netdata
sudo dnf install --refresh netdata

openSUSE

Switch from Nightly to Stable

# Install stable repository (automatically removes nightly repo)
sudo zypper install --allowerasing netdata-repo
sudo zypper refresh
sudo zypper remove netdata
sudo zypper install netdata

Switch from Stable to Nightly

# Install nightly repository (automatically removes stable repo)
sudo zypper install --allowerasing netdata-repo-edge
sudo zypper refresh
sudo zypper remove netdata
sudo zypper install netdata

tip

When switching release channels with native packages, the repository configuration packages automatically handle the removal of the previous channel's repository to prevent conflicts.