https://linen.dev logo
Join Slack
Powered by
I recently moved the directory of my airbyte folde...
# replication-ask-ai
n
I recently moved the directory of my airbyte folder in a new one. How can I fix this error: invalid mount configuration for type bind: bind source path does not exist
k
New message text here
n
@kapa.ai okay so if I installed airbyte in Folder1 originally and then moved it into Subfolder2. Would I make those roots: /Subfolder2/tmp
k
Based on the information provided in the extracts, if you have moved your Airbyte installation to a different folder, you would need to update the 
LOCAL_ROOT
, 
LOCAL_DOCKER_MOUNT
, and 
HACK_LOCAL_ROOT_PARENT
values in the 
.env
file in your local Airbyte root folder. These should be set to the absolute path of the new location on your machine. For example, if you moved Airbyte to 
Subfolder2
, you would set these values to the path of 
Subfolder2
. If 
Subfolder2
is located in 
Folder1
, the path would be 
/Folder1/Subfolder2
. Remember to replace colons in the path with a double forward slash, 
//
. 
LOCAL_ROOT
& 
LOCAL_DOCKER_MOUNT
should be set to the same value, and 
HACK_LOCAL_ROOT_PARENT
should be set to their parent directory. Here is the extract that provides this information: > Currently, the local storage URL for reading must start with the local mount "/local/". Please note that if you are replicating data from a locally stored file on Windows OS, you will need to open the 
.env
file in your local Airbyte root folder and change the values for: > - 
LOCAL_ROOT
> - 
LOCAL_DOCKER_MOUNT
> - 
HACK_LOCAL_ROOT_PARENT
> Please set these to an existing absolute path on your machine. Colons in the path need to be replaced with a double forward slash, 
//
. 
LOCAL_ROOT
& 
LOCAL_DOCKER_MOUNT
should be set to the same value, and 
HACK_LOCAL_ROOT_PARENT
should be set to their parent directory. [source](https://docs.airbyte.com/integrations/sources/file) Please note that the 
/tmp
directory mentioned in the extracts is the default location where Airbyte writes data when using local file-based destinations. If you want to change this location, you would need to update the 
destination_path
in your configuration. [source](https://docs.airbyte.com/integrations/destinations/local-json)
n
@kapa.ai where can I find the destination_path
k
A message from kapa.ai
The 
destination_path
is a parameter that you set when configuring a destination in Airbyte. Here's how you can find and set it: 1. Log in to your Airbyte dashboard. 2. Click on the Destinations tab in the navigation bar found on the left side of the dashboard. 3. If you're adding a new destination, click on + New destination. If you're updating an existing destination, click on the destination you want to update. 4. On the destination setup page, you'll see a set of fields that you need to fill out. One of these fields is the Destination Path. This is where you set the 
destination_path
. For example, if you're setting up a Local JSON, Local CSV, or SQLite destination, the 
destination_path
will always start with 
/local
whether it is specified by the user or not. Any directory nesting within local will be mapped onto the local mount. By default, the 
LOCAL_ROOT
env variable in the 
.env
file is set 
/tmp/airbyte_local
. The local mount is mounted by Docker onto 
LOCAL_ROOT
. This means the 
/local
is substituted by 
/tmp/airbyte_local
by default. [source](https://docs.airbyte.com/integrations/destinations/local-json) If you're setting up an R2 destination, the 
destination_path
would be the R2 Bucket Path, which is a subdirectory under the R2 bucket where you want to sync the data into. [source](https://docs.airbyte.com/integrations/destinations/r2) Please refer to the setup guide provided on the right side of the destination setup page for specific details on the nature of each field.
2 Views
Open in Slack
PreviousNext
Powered by