# Why do relative bind mounts appear empty after updating a stack that was deployed from Git?

When a stack deployed from a Git repository is updated, Portainer re-clones the repository if the commit has changed. This removes and recreates the repository directory on the host. If a container uses a relative path bind mount that points to files or directories inside the Git repository and that container is not recreated during the update, the bind mount can appear empty inside the container. This happens because the container is still referencing the previous filesystem path, which no longer exists after the repository is re-cloned.

Containers are only recreated when their Compose file or related configuration changes, unless [GitOps Updates with Force redeployment](/sts/user/docker/stacks/add.md#option-3-git-repository) is enabled. If a configuration file mounted by a service changes, Portainer will restart the affected service during the GitOps update so the updated configuration is applied.

To ensure bind mounts are remounted correctly, [update the stack](/sts/user/docker/stacks/edit.md) using **Pull and redeploy** with **Re-pull image and redeploy** enabled. This forces all containers in the stack to be recreated and remounts bind mounts against the newly cloned repository.

<div><figure><img src="/files/FriYgaGcDnBoGkVj2WPn" alt=""><figcaption></figcaption></figure> <figure><img src="/files/SkoWno45JuYHOXxEvZqM" alt=""><figcaption></figcaption></figure></div>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.portainer.io/sts/faqs/troubleshooting/stacks-deployments-and-updates/empty-relative-bind-mounts.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.