> For the complete documentation index, see [llms.txt](https://ai-docs.fptcloud.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ai-docs.fptcloud.com/fpt-gpu-cloud/gpu-container.md).

# GPU Container

### What is GPU Container? <a href="#contentify_0" id="contentify_0"></a>

GPU Container is a managed compute platform that lets you run containers directly on top of FPT’s AI Factory infrastructure. With just a few clicks, you can deploy and manage AI workloads effortlessly—whether by using your own container images or leveraging the built-in images provided by FPT.

### How does it work? <a href="#contentify_1" id="contentify_1"></a>

A GPU container runs applications in an isolated environment with direct access to GPU resources. It uses tools like the NVIDIA Container Toolkit to leverage GPU acceleration for tasks like AI, ML, or data processing—without complex setup.

### Why GPU container? <a href="#contentify_2" id="contentify_2"></a>

1. **Containerized AI Deployment:** Runs AI workloads in containers.
2. **High-Performance GPU Compute:** Access to NVIDIA GPUs for AI/ML workloads.
3. **Quick Deployment**: Spin up a container with a powerful GPU in 1 click using our built-in templates.
4. **Persistent Storage**: This storage is persistent and will be available even if the container is stopped.


---

# 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://ai-docs.fptcloud.com/fpt-gpu-cloud/gpu-container.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.
