> For the complete documentation index, see [llms.txt](https://docs.fluentbit.io/manual/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fluentbit.io/manual/1.6/installation/supported-platforms.md).

# Supported Platforms

The following operating systems and architectures are supported in Fluent Bit.

| Operating System | Distribution                                                                                 | Architectures    |
| ---------------- | -------------------------------------------------------------------------------------------- | ---------------- |
| Linux            | [Amazon Linux 2](/manual/1.6/installation/linux/amazon-linux.md)                             | x86\_64, Arm64v8 |
|                  | [Centos 8](/manual/1.6/installation/linux/redhat-centos.md)                                  | x86\_64, Arm64v8 |
|                  | [Centos 7](/manual/1.6/installation/linux/redhat-centos.md)                                  | x86\_64, Arm64v8 |
|                  | [Debian 10 (Buster)](/manual/1.6/installation/linux/debian.md)                               | x86\_64, Arm64v8 |
|                  | [Debian 9 (Stretch)](/manual/1.6/installation/linux/debian.md)                               | x86\_64, Arm64v8 |
|                  | [Debian 8 (Jessie)](/manual/1.6/installation/linux/debian.md)                                | x86\_64, Arm64v8 |
|                  | [Nixos](https://github.com/NixOS/nixpkgs/blob/master/pkgs/tools/misc/fluent-bit/default.nix) | x86\_64, Arm64v8 |
|                  | [Ubuntu 20.04 (Focal Fossa)](/manual/1.6/installation/linux/ubuntu.md)                       | x86\_64, Arm64v8 |
|                  | [Ubuntu 18.04 (Bionic Beaver)](/manual/1.6/installation/linux/ubuntu.md)                     | x86\_64, Arm64v8 |
|                  | [Ubuntu 16.04 (Xenial Xerus)](/manual/1.6/installation/linux/ubuntu.md)                      | x86\_64          |
|                  | [Raspbian 10 (Buster)](/manual/1.6/installation/linux/raspbian-raspberry-pi.md)              | Arm32v7          |
|                  | [Raspbian 9 (Stretch)](/manual/1.6/installation/linux/raspbian-raspberry-pi.md)              | Arm32v7          |
|                  | [Raspbian 8 (Jessie)](/manual/1.6/installation/linux/raspbian-raspberry-pi.md)               | Arm32v7          |
| Windows          | [Windows Server 2019](/manual/1.6/installation/windows.md)                                   | x86\_64, x86     |
|                  | [Windows 10 1903](/manual/1.6/installation/windows.md)                                       | x86\_64, x86     |

From an architecture support perspective, Fluent Bit is fully functional on x86\_64, Arm64v8 and Arm32v7 based processors.

Fluent Bit can work also on OSX and \*BSD systems, but not all plugins will be available on all platforms. Official support will be expanding based on community demand.


---

# 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://docs.fluentbit.io/manual/1.6/installation/supported-platforms.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.