Remove port 8220 from docker-compose configuration (#37004)

This port is not actually needed.

---------

Co-authored-by: Dale Ribeiro <dale@fleetdm.com>
This commit is contained in:
kitzy 2025-12-15 10:27:09 -05:00 committed by GitHub
parent 3bbad16c36
commit 5e95a5eb4a
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
2 changed files with 3 additions and 7 deletions

View file

@ -8,7 +8,7 @@ This guide walks you through deploying Fleet using Docker Compose. You'll have a
- [Docker](https://docs.docker.com/engine/install/) and [Docker Compose](https://docs.docker.com/compose/install/) installed
- Ports 1337, 8220, 3306, and 6379 available
- Ports 1337, 3306, and 6379 available
- Basic command line familiarity
@ -210,10 +210,7 @@ This deployment includes three services and one initialization container:
## Ports
Devices connect to Fleet on ports 1337 and 8220. If you're running Fleet on a server, update your firewall to allow:
- Port 1337 (web UI and API)
- Port 8220 (device connections)
Devices connect to Fleet on port 1337. If needed, update your firewall to allow inbound connections on port 1337.
## View logs
@ -304,7 +301,7 @@ Both `fleet.crt` and `fleet.key` should exist and be readable. If using Option 1
**Devices won't connect**
Ensure ports 1337 and 8220 are accessible from your devices. Check your firewall and network configuration.
Ensure port 1337 is accessible from your devices. Check your firewall and network configuration.
If using self-signed certificates, devices need the certificate installed or TLS verification disabled (not recommended for production).

View file

@ -100,7 +100,6 @@ services:
- FLEET_S3_SOFTWARE_INSTALLERS_REGION=${FLEET_S3_SOFTWARE_INSTALLERS_REGION}
ports:
- "${FLEET_SERVER_PORT}:${FLEET_SERVER_PORT}" # UI/API
- "8220:8220" # osquery enroll/TLS endpoint
volumes:
- data:/fleet
- logs:/logs