Shawn Maddock

09/16/2022, 7:40 PM
fleetctl setup
documentation and help text says it takes a
argument with a path to a config file, but if I include that flag I get:
Error: set the Fleet API address with: fleetctl config set --address <https://localhost:8080>
If I run setup without the config file and then
fleetctl apply -f
the config file, it works. I don’t see any open bug reports, has anyone else seen this or can confirm the behavior, or let me know what I’m doing wrong?
Since the docs say “fleetctl config file” I assume it’s referring to the app config file that’s usable by
and not the
server config file…
I just tried specifying the
server config instead and that gives me the same error

Michal Nicpon

09/19/2022, 4:39 PM
By default,
will use a config file located at
. You can create one at the default location with the fleet server address configured by running
fleetctl config set --address <>
After that,
fleetctl setup
should work for you. Let me know if you have any further issues.
note that the fleetctl config file is different from the fleet server config file