FAQ

Why a single container?

This image is designed for simplicity and fast setup. Everything Fleet needs runs together, with one volume and one set of environment variables.

Can I change the Fleet port?

The container uses Fleet’s default port 1337. If you want a different external port, map it:

-p 8080:1337

Does the container support TLS?

Yes. You can enable TLS with FLEET_SERVER_TLS=true and provide cert/key paths. See TLS & MDM.

Can I use my own database?

This image expects the bundled MySQL and Redis services. If you want external services, use the official Fleet Docker Compose setup.

Does this support ARM?

Yes. The image is built for both linux/amd64 and linux/arm64.

Is FLEET_PASSWORD the same as my Fleet login?

No. FLEET_PASSWORD is used internally for MySQL and Redis. Your Fleet web UI login is created on the setup screen.

Do I really need the server private key?

Yes. This image requires FLEET_SERVER_PRIVATE_KEY to start, and it must be at least 32 bytes.

Where is the data and logs stored?

Everything lives under /data inside the container:

• /data/mysql
• /data/redis
• /data/logs/<service>