Elgato_dark/fleet
1
0
Fork 0
mirror of https://github.com/fleetdm/fleet synced 2026-04-21 13:37:30 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 91

Adjust to meet Fleet style and voice (#43201)

Browse source 
Made adjustments to fix violations of Fleet style, tone, and voice. Also
fixed a small version accuracy error.
This commit is contained in:
Dan Gordon 2026-04-07 21:21:01 -07:00 committed by GitHub
parent 1e940071bc
commit 630bb25448
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 24 additions and 24 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

48
articles/deploy-fleet-on-proxmox.md
View file

@ -1,34 +1,34 @@
# Deploy Fleet on Proxmox
[Proxmox](https://www.proxmox.com/en/) is an open source virtualization platform that is widely adopted for on-premises and private cloud virtualization. Many organizations have adopted Proxmox due to cost and licensing changes with other virtualization platforms.
[Proxmox](https://www.proxmox.com/en/) is an open source virtualization platform widely adopted for on-premises and private cloud deployments. Many organizations have moved to Proxmox due to cost and licensing changes with other hypervisors. If you're running a homelab or evaluating Fleet before a broader rollout, it's a practical place to stand up a Fleet server. You get a real deployment, on hardware you own, without depending on a cloud provider.
This tutorial describes how to deploy the Fleet server on Proxmox using Ubuntu and Docker. The configuration uses a self-signed certificate and is appropriate for a small deployment, evaluation, or lab environment. The same concepts used in this tutorial can be applied to larger deployments using additional VMs for scale.
This tutorial walks you through deploying Fleet on Proxmox using Ubuntu and Docker Compose, with a self-signed certificate. It's appropriate for small deployments, evaluations, and lab environments. The same concepts apply to larger deployments using additional VMs for scale.
Deploying Fleet on Proxmox requires 5 steps:
1. Deploy a Proxmox Virtual Machine
1. Deploy a Proxmox virtual machine
2. Install Ubuntu
3. Install Docker
4. Deploy Fleet using Docker Compose
5. Complete the Fleet Setup Wizard
5. Complete the Fleet setup wizard
The following sections take you through each step with the necessary commands. Your environment may differ slightly. You should still be able to follow along and end up with a working Fleet installation.
The following sections take you through each step, with all necessary screenshots and commands. While the nuances in your environment might be slightly different, you should be able to follow along to build a complete Fleet installation.
## Prerequisites
You will need the following to complete this installation tutorial:
To complete this installation, have the following ready:
- A running **Proxmox VE host** (version 7.x or 8.x)
- At least **4 GB RAM** and **2 vCPUs** available to allocate to the Fleet VM
- At least **20 GB of disk space** for the VM
- A **domain name or local DNS entry** pointing to the VM's IP (required for TLS/MDM enrollment)
- A running Proxmox VE host (version 7.x or 8.x)
- At least 4 GB RAM and 2 vCPUs available to allocate to the Fleet VM
- At least 20 GB of disk space for the VM
- A domain name or local DNS entry pointing to the VM's IP (required for TLS/MDM enrollment)
- Basic familiarity with the Proxmox web UI and Linux command line
Additionally, the Fleet server and clients must be able to communicate over TLS on the default port of 1337.
- The Fleet server and clients must communicate over TLS on port 1337
## Create a virtual machine in Proxmox
The first step is to deploy a virtual machine to host the Fleet server. Fleet can be deployed using Docker Compose, and any Linux distribution with Docker support is acceptable. This tutorial uses an Ubuntu 26.04 server image.
The first step is to deploy a virtual machine to host the Fleet server. You can deploy Fleet using Docker Compose on any Linux distribution with Docker support. This tutorial uses an Ubuntu 24.04 server image.
First, upload the ISO to Proxmox by navigating to your desired storage location and selecting **ISO Images > Download from URL**. Specify the URL to an appropriate ISO, such as https://releases.ubuntu.com/24.04.4/ubuntu-24.04.4-live-server-amd64.iso
@ -60,9 +60,9 @@ First, boot the VM in Proxmox by navigating to the VM and clicking **Console > S
## Install Docker and Docker Compose
Fleet runs as a set of Docker containers and can be managed using [Docker Compose](https://docs.docker.com/compose/). The operating system may already have Docker in its package repository. However, the best way to get the latest version of Docker is by using the official Docker repositories.
Fleet runs as a set of Docker containers and you can managed it using [Docker Compose](https://docs.docker.com/compose/). The operating system may already have Docker in its package repository. However, the best way to get the latest version of Docker is by using the official Docker repositories.
The installation instructions below are accurate for Ubuntu at this time of writing. However, it’s always a good idea to consult the [official installation instructions](https://docs.docker.com/engine/install/ubuntu/) first.
The installation instructions below are accurate for Ubuntu at this time of writing. Consult the [official installation instructions](https://docs.docker.com/engine/install/ubuntu/) for the most updated steps.
First, update the package manager index and install the prerequisite software for adding the Docker repository:
@ -127,7 +127,7 @@ This message shows that your installation appears to be working correctly.
## Deploy Fleet using Docker Compose
Fleet is hosted using a set of Docker containers deployed with Docker Compose. This makes it easy to manage your Fleet deployment without worrying about host-level package dependencies and configuration. Deploying Fleet using Docker Compose is simple and fast.
Fleet is hosted using a set of Docker containers deployed with Docker Compose. This makes it easy to manage your Fleet deployment without worrying about host-level package dependencies and configuration.
### Set up the Fleet Docker Compose environment
@ -173,10 +173,10 @@ The .env file is used to customize Fleet’s configuration. There are several op
| **Environment Variable** | **Value** |
| :---- | :---- |
| MYSQL\_ROOT\_PASSWORD | A root password for the MySQL database. This root password will be set when Docker creates the MySQL container. Make sure this password meets your organization’s password complexity requirements. |
| MYSQL\_PASSWORD=SecurePassword123 | A password for the “fleet’ user in the MySQL database. This password will be set when Docker creates the MySQL container. Make sure this password meets your organization’s password complexity requirements. |
| MYSQL\_ROOT\_PASSWORD | A root password for the MySQL database. Docker sets this password when it creates the MySQL container. Make sure this password meets your organization’s password complexity requirements. |
| MYSQL\_PASSWORD=SecurePassword123 | A password for the `fleet` user in the MySQL database. Docker sets this password when it creates the MySQL container. Make sure this password meets your organization’s password complexity requirements. |
| FLEET\_SERVER\_PRIVATE\_KEY | The private key used by the Fleet server. This should be the output of the previous openssl command. |
| FLEET\_LICENSE\_KEY | A license key for Fleet Premium. This is an **optional** field, and you can leave it blank to use [Fleet’s free tier](https://fleetdm.com/try-fleet). |
| FLEET\_LICENSE\_KEY | A license key for Fleet Premium. This is an optional field, and you can leave it blank to use [Fleet’s free tier](https://fleetdm.com/try-fleet). |
Edit the .env file using your preferred editor, such as vim. Sample values are shown below, but you should customize these for your environment.
@ -196,7 +196,7 @@ FLEET_SERVER_PRIVATE_KEY=qqM+mPLALkc4Uc+cTifMoBQKmmrt2rhcUe85klaPif0=
Certificates are a crucial part of securing the connection between the Fleet server and its clients. You must provide the Fleet installation with a certificate for the Fleet server to use. This tutorial uses a self-signed certificate, which is appropriate for demo and evaluation environments.
For more information about the way certificates are handled in Fleet, please see the following documentation: https://fleetdm.com/guides/certificates-in-fleetd
See the Fleet certificates documentation (https://fleetdm.com/guides/certificates-in-fleetd) for more information about the way certificates are handled in Fleet.
First, create a directory to store the certificate and private key:
@ -204,7 +204,7 @@ First, create a directory to store the certificate and private key:
sudo mkdir certs
```
Next, generate a certificate and private key. You must customize the CN and subjectAltName fields to use the fully-qualified domain name (FQDN) and IP address of your Fleet installation. Configuring the subjectAltName field is particularly important, as the CN field is used only for legacy purposes and will not enable successful certificate validation on its own.
Next, generate a certificate and private key. You must customize the CN and subjectAltName fields to use the fully-qualified domain name (FQDN) and IP address of your Fleet installation. The `subjectAltName` field is required for certificate validation. The `CN` field is kept for legacy purposes only and won't validate on its own.
```bash
sudo openssl req -x509 -nodes -days 365 -newkey rsa:2048 \
@ -246,15 +246,15 @@ These steps include:
3. Setting up the Fleet web address
- This should be set to the fully-qualified domain name (FQDN) of your Fleet server. Clients will use this web address to connect with Fleet
Once you have fully configured Fleet, you will be automatically redirected to the main server dashboard.
Once you have fully configured Fleet, it will redirect you to the main server dashboard.
![Main server dashboard](../website/assets/images/articles/deploy-fleet-on-proxmox-3-500x302@2x.png)
## Next steps
Getting started with Fleet on Proxmox is easy, thanks to Fleet’s container-native architecture and support for Docker Compose. In this tutorial, you deployed a Fleet server running inside of an Ubuntu VM on Proxmox, as a simple environment that is appropriate for evaluation. Larger environments should consult the [Fleet Reference Architectures guide](https://fleetdm.com/docs/deploy/reference-architectures) to understand production considerations.
Fleet’s container-native architecture and support for Docker Compose makes it quick to get started with Fleet on Proxmox. In this guide, you deployed a Fleet server running inside of an Ubuntu VM on Proxmox, as a simple environment that is appropriate for evaluation. Larger environments should consult the [Fleet Reference Architectures guide](https://fleetdm.com/docs/deploy/reference-architectures) to understand production considerations.
Now that Fleet has been successfully deployed in your Proxmox environment, you can begin [enrolling hosts](https://fleetdm.com/guides/enroll-hosts) and [exploring the rich set of MDM capabilities](https://fleetdm.com/docs/get-started/tutorials-and-guides#further-learning) that Fleet has to offer.
Now that Fleet has been successfully deployed in your Proxmox environment, you can begin [enrolling hosts](https://fleetdm.com/guides/enroll-hosts) and [exploring Fleet's MDM capabilities](https://fleetdm.com/docs/get-started/tutorials-and-guides#further-learning).