> For the complete documentation index, see [llms.txt](https://run-ai-docs.nvidia.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://run-ai-docs.nvidia.com/self-hosted/2.22/infrastructure-setup/advanced-setup/git-and-s3-sidecar-containers.md).

# Git and S3 Sidecar Containers

NVIDIA Run:ai enables AI practitioners to integrate with S3 or Git as data sources. When using a custom CA, sidecar containers used for S3 or Git integrations do not automatically inherit the CA configured at the cluster level. This requires manually building a custom container for each integration based on the default NVIDIA Run:ai image while incorporating the local CA certificates.

1. [Build tag and publish](https://docs.docker.com/get-started/docker-concepts/building-images/build-tag-and-publish-an-image/) the images for the S3 / Git integrations using the following Dockerfile:

   ```bash
   #FROM gcr.io/run-ai-prod/goofys:master # S3
   #FROM registry.k8s.io/git-sync/git-sync:v4.4.0 # Git
   USER root
   ADD <ca_bundle_path> /usr/local/share/ca-certificates/ # example: anchors/
   RUN chmod 644 -R /usr/local/share/ca-certificates/ && update-ca-certificates
   WORKDIR /
   ENTRYPOINT ["sh"]
   CMD ["/usr/bin/run.sh"]
   ```
2. Edit the cluster configurations for images used by NVIDIA Run:ai following the [S3 and Git sidecar images](/self-hosted/2.22/infrastructure-setup/advanced-setup/cluster-config.md#s3-and-git-sidecar-images) instructions.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://run-ai-docs.nvidia.com/self-hosted/2.22/infrastructure-setup/advanced-setup/git-and-s3-sidecar-containers.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.