Clarifying the possible installation types (#15958)
Signed-off-by: Tasos Katsoulas <tasos@netdata.cloud> Co-authored-by: Ilya Mashchenko <ilya@netdata.cloud>
Tasos Katsoulas committed
Sep 13, 2023 at 15:49 UTC
db25063e9018078354e8063bc962f8596145071c
1 file changed
+16
packaging/installer/UPDATE.md
+16
@@ -31,6 +31,22 @@ Starting with netdata v1.33.0, you can use Netdata itself to determine the insta
31
netdata -W buildinfo | grep -E 'Installation Type|Install type:'
32
```
33
34
+The following table contains all possible installation types:
35
+
36
+| Installation-type | Description |
37
+|--------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------|
38
+| binpkg-rpm | RPM-based native packages shipped from Netdata's repos. |
39
+| binpkg-deb | DEB-based native packages shipped from Netdata's repos. |
40
+| kickstart-build | Build from source with the kickstart script's `--build-only` option. |
41
+| kickstart-static | Installed the static builds, shipped from netdata via the kickstart script's (option: `--static-only`). |
42
+| manual-static-ARCH | Manually installed static Agent binaries by downloading archives from GitHub and installing them manually. Offline installations are part of this category. |
43
+| legacy-build | Used for pre-existing kickstart.sh or netdata-installer.sh installations. This exist because we cannot determine how the install originally happened. |
44
+| legacy-static | Same as legacy-build, but for static installs. |
45
+| oci | Installed using official Docker images from Netdata, though not necessarily running on Docker |
46
+| custom | Anything not covered by the other identifiers, including manual builds, manually running netdata-installer.sh, and third-party packages (community). |
47
+| Unknown | Same as custom. |
48
+
49
+
50
If you are using an older version of Netdata, or the above command produces no output, you can run our one-line
51
installation script in dry-run mode to attempt to determine what method to use to update by running the following
52
command: