# How to convert a Docker install to a native install?
**URL:** https://community.netdata.cloud/t/how-to-convert-a-docker-install-to-a-native-install/1500
**Category:** Help
**Tags:** agent
**Created:** [July 3, 2021, 10:38am UTC](https://community.netdata.cloud/t/how-to-convert-a-docker-install-to-a-native-install/1500 "2021-07-03T10:38:12Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@tmladek](https://community.netdata.cloud/u/tmladek)
#### Post date: [July 3, 2021, 10:38am UTC](https://community.netdata.cloud/t/how-to-convert-a-docker-install-to-a-native-install/1500/1 "2021-07-03T10:38:12Z")
I initially installed netdata on this machine using Docker and it works just fine, but I realized I’d like to run it “directly on the metal” because of, for instance, GPU monitoring, etc.
How do I best “convert” the install to a native one? I mainly don’t want to lose the association on Netdata Cloud, since it’s added in all these war rooms and dashboards, etc; Netdata config files I can transfer over fine.
Thanks in advance!
---
### Author:  [@Austin\_Hemmelgarn](https://community.netdata.cloud/u/Austin_Hemmelgarn)
#### Post date: [July 3, 2021, 12:36pm UTC](https://community.netdata.cloud/t/how-to-convert-a-docker-install-to-a-native-install/1500/2 "2021-07-03T12:36:23Z")
The relevant directories you would need to copy out of the container to the host are `/var/lib/netdata/registry` (this contains the machine GUID information, which needs to stay the same for the cloud to work) and `/var/lib/netdata/cloud.d` (this contains the actual cloud configuration). Provided you copy those _exactly_, the native install should be able to connect to the cloud using the exact same credentials. Just make sure you don’t run the container at the same time as the native install, as that might confuse the cloud.
---
### Author:  [@tmladek](https://community.netdata.cloud/u/tmladek)
#### Post date: [July 3, 2021, 5:06pm UTC](https://community.netdata.cloud/t/how-to-convert-a-docker-install-to-a-native-install/1500/3 "2021-07-03T17:06:14Z")
> [@Austin\_Hemmelgarn](#):
>
> Just make sure you don’t run the container at the same time as the native install, as that might confuse the cloud.
Well, despite trying to remember this warning it slipped my mind, but no worries - the native install simply didn’t even come up because it couldn’t bind to the ports occupied by the docker install 🙃
Anyway, this is precisely what I needed and it worked just fine, many thanks!