# kickstart.sh random install to either /etc/netdata or /opt/netdata/etc/netdata

**URL:** <https://community.netdata.cloud/t/kickstart-sh-random-install-to-either-etc-netdata-or-opt-netdata-etc-netdata/3655>\
**Category:** Help\
**Created:** [December 18, 2022, 6:04am UTC](https://community.netdata.cloud/t/kickstart-sh-random-install-to-either-etc-netdata-or-opt-netdata-etc-netdata/3655 "2022-12-18T06:04:21Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Austin\_Hemmelgarn](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.netdata.cloud/austin_hemmelgarn/32/4495_2.png) [@Austin\_Hemmelgarn](https://community.netdata.cloud/u/Austin_Hemmelgarn)\
**Post date:** [December 18, 2022, 1:45pm UTC](https://community.netdata.cloud/t/kickstart-sh-random-install-to-either-etc-netdata-or-opt-netdata-etc-netdata/3655/2 "2022-12-18T13:45:05Z")

</div>

With that exact set of options, you actually should be getting a fatal error about the use of `--install-prefix` without `--build-only` (we are only able to support custom install prefixes when building locally).

If you just want things under `/opt`, you can achieve that by forcing use of a static build using the `--static-only`option (without the `--install-prefix` option), or by adding `--build-only` to the list of options you’re passing the kickstart script.

If you just want things under `/`, you can enforce that by either:

- Ensuring the systems in question have a working internet connection and can reliably access [https://packagecloud.io](https://packagecloud.io) (note though that this will change to [https://repos.netdata.cloud](https://repos.netdata.cloud) at some point within the next few months), and then using the `--native-only` option without any `--install-prefix` option. This will use native DEB packages, allowing you to manage updates with APT.

or:

- Using `--build-only` to build locally, without using any `--install-prefix` option.

* * *

As far as why you’re seeing this inconsistent behavior, my guess is that you’ve got issues with your internet connection that are preventing reliable access to [https://packagecloud.io](https://packagecloud.io). If that access happens to work, you end up with a native package (which installs under `/`), if it fails at any of about half a dozen points during the install the installer will instead fall back to a static build (which installs under `/opt/netdata`).

---

_[View the full topic](https://community.netdata.cloud/t/kickstart-sh-random-install-to-either-etc-netdata-or-opt-netdata-etc-netdata/3655)._