# Confiugure Kurl.sh core directories into a custom location

**URL:** <https://community.replicated.com/t/confiugure-kurl-sh-core-directories-into-a-custom-location/1256>\
**Category:** Supporting your customers\
**Tags:** kurl\
**Created:** [July 18, 2023, 2:54am UTC](https://community.replicated.com/t/confiugure-kurl-sh-core-directories-into-a-custom-location/1256 "2023-07-18T02:54:36Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ahsan\_Shamsudeen](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.replicated.com/ahsan_shamsudeen/32/682_2.png) [@Ahsan\_Shamsudeen](https://community.replicated.com/u/Ahsan_Shamsudeen)\
**Post date:** [July 18, 2023, 2:54am UTC](https://community.replicated.com/t/confiugure-kurl-sh-core-directories-into-a-custom-location/1256/1 "2023-07-18T02:54:36Z")

</div>

Is there any possible options/configurations to install below [Kurl.sh](http://Kurl.sh) core directories into a custom location ? For ex , /var/lib into /var/lib/docker or some other location.

 ![Screenshot 2023-07-17 at 21.09.58](https://canada1.discourse-cdn.com/flex030/uploads/replicated/original/1X/348a1e9a727aefc7ecf401114ddafbc14d2c6155.png)  
[https://kurl.sh/docs/install-with-kurl/system-requirements#disk-space-requirements](https://kurl.sh/docs/install-with-kurl/system-requirements#disk-space-requirements)

---

<div class="post-metadata">

**Author:** ![Dexter\_Yan](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.replicated.com/dexter_yan/32/661_2.png) [@Dexter\_Yan](https://community.replicated.com/u/Dexter_Yan)\
**Post date:** [July 18, 2023, 5:50am UTC](https://community.replicated.com/t/confiugure-kurl-sh-core-directories-into-a-custom-location/1256/2 "2023-07-18T05:50:33Z")

</div>

Hi @Ahsan_Shamsudeen,

We don’t provide a overall configuration that you can install all core directories of kURL into a custom location. However, you can still store data in a directory other than `/var/lib` by each. For example, if you are going to use the directory `/usr/local/docker` as an alternative, a detailed instruction is in [Does replicated support storing data in a location other than /var/lib?](https://community.replicated.com/t/does-replicated-support-storing-data-in-a-location-other-than-var-lib/224). Those configuration is case-by-case.

---

<div class="post-metadata">

**Author:** ![hemen.kapadia](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.replicated.com/hemen.kapadia/32/684_2.png) [@hemen.kapadia](https://community.replicated.com/u/hemen.kapadia)\
**Post date:** [July 18, 2023, 6:29pm UTC](https://community.replicated.com/t/confiugure-kurl-sh-core-directories-into-a-custom-location/1256/3 "2023-07-18T18:29:34Z")

</div>

Hi Dex, thanks for the guidance.

Can you provide more details about the below requirement for root filesystem ? If there are separate mount points created for /var etc does root (/) need to be 100GB ? Would anything be stored in / as almost everything is in /var.

Reference - Table at [https://kurl.sh/docs/install-with-kurl/system-requirements#core-requirements](https://kurl.sh/docs/install-with-kurl/system-requirements#core-requirements) for the above query.

 ![image](https://canada1.discourse-cdn.com/flex030/uploads/replicated/original/1X/fa44e4ff65d51d4ff14bd645dc6f95d3f71c60b8.png)

Regards,  
Hemen

---

<div class="post-metadata">

**Author:** ![adamancini](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.replicated.com/adamancini/32/229_2.png) [@adamancini](https://community.replicated.com/u/adamancini)\
**Post date:** [July 18, 2023, 7:49pm UTC](https://community.replicated.com/t/confiugure-kurl-sh-core-directories-into-a-custom-location/1256/4 "2023-07-18T19:49:57Z")

</div>

@hemen.kapadia The instructions here assume that all of `/var` is part of the root filesystem `/` on a single partition. So if you create a new partition or mount point for `/var` I would consider making it at least 100GB according to the recommendation here. Your root filesystem `/` then, should contain adequate space for the OS, home folders, etc.

---

<div class="post-metadata">

**Author:** ![ethanm](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.replicated.com/ethanm/32/11_2.png) [@ethanm](https://community.replicated.com/u/ethanm)\
**Post date:** [February 18, 2025, 8:25pm UTC](https://community.replicated.com/t/confiugure-kurl-sh-core-directories-into-a-custom-location/1256/5 "2025-02-18T20:25:19Z")

</div>

The docs that are linked above in @Dexter_Yan 's reply are for Replicated’s legacy [Classic](https://help.replicated.com/docs/native/getting-started/overview/) product, not kURL.

> [@Does replicated support storing data in a location other than /var/lib?](https://community.replicated.com/t/does-replicated-support-storing-data-in-a-location-other-than-var-lib/224):
>
> In the circumstance where a customer wants to store data in a directory other than /var/lib (/var/lib/replicated, /var/lib/replicated-operator or /var/lib/docker), we usually suggest bind mounts when it is an option. Replicate does not currently support the dockerd data-root [option](https://docs.docker.com/v17.09/engine/reference/commandline/dockerd/). For example if you wanted to use the directory /usr/local/docker as an alternative we could bind mount it to the destination using the following command: mount --bind /usr/local/docker /var/lib/docker In order to …
