1.8 KiB
Contribution FAQ
Enrolling in multiple Fleet servers
Enrolling your device with more than one Fleet server is not currently possible. Multiple install roots are useful for the development of Fleet itself but complex to maintain. While this has some value for Fleet contributors, there is currently no active effort to add and maintain support for multiple enrollments from the same device.
Make errors
dep: command not found
/bin/bash: dep: command not found
make: *** [.deps] Error 127
If you get the above error, you need to add $GOPATH/bin to your PATH. A quick fix is to run export PATH=$GOPATH/bin:$PATH.
See the Go language documentation for workspaces and GOPATH for more in-depth documentation.
undefined: Asset
server/fleet/emails.go:90:23: undefined: Asset
make: *** [fleet] Error 2
If you get an undefined: Asset error, it is likely because you did not run make generate before make build. See Building Fleet for additional documentation on compiling the fleet binary.
Adding hosts for testing
The osquery directory contains a docker-compose.yml and additional configuration files to start containerized osquery agents.
To start osquery, first retrieve the "Enroll secret" from Fleet (by clicking the "Add New Host") button in the Fleet dashboard, or with fleetctl get enroll-secret).
cd tools/osquery
ENROLL_SECRET=<copy from fleet> docker-compose up