From 9b3a4f79f3df9be3a2cec87a549a64b5b805e7bb Mon Sep 17 00:00:00 2001
From: Naveen Kumar Vadlamudi
 <39674418+VadlamudiNaveen@users.noreply.github.com>
Date: Sun, 11 Jun 2023 11:40:58 -0600
Subject: [PATCH] Added Note for Local File System Ingestion (ingest-dbt-ui.md)
 (#11958)

The following note provides, more clarification for the users that are trying to ingest data from dbt to Openmetadata.
---
 .../connectors/ingestion/workflows/dbt/ingest-dbt-ui.md     | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/openmetadata-docs/content/v1.0.0/connectors/ingestion/workflows/dbt/ingest-dbt-ui.md b/openmetadata-docs/content/v1.0.0/connectors/ingestion/workflows/dbt/ingest-dbt-ui.md
index 64bf40efeb5..42b547d801f 100644
--- a/openmetadata-docs/content/v1.0.0/connectors/ingestion/workflows/dbt/ingest-dbt-ui.md
+++ b/openmetadata-docs/content/v1.0.0/connectors/ingestion/workflows/dbt/ingest-dbt-ui.md
@@ -90,6 +90,12 @@ For more information on Google Cloud Storage authentication click [here](https:/
 
 Path of the `manifest.json`, `catalog.json` and `run_results.json` files stored in the local system or in the container in which openmetadata server is running can be directly provided.
 
+{% note %}
+
+The files present in local system repository where DBT is hosted, cannot be accessed from the Openmetadata container file system. Instead one should setup a process such that `manifest.json`, `catalog.json` are updated periodically in Openmetadata container file system.
+
+{% /note %}
+
 {% image
   src="/images/v1.0.0/features/ingestion/workflows/dbt/local-storage.png"
   alt="local-storage"