documentation and help text says it takes a
argument with a path to a config file, but if I include that flag I get:
If I run setup without the config file and then
Error: set the Fleet API address with: fleetctl config set --address <https://localhost:8080>
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?
fleetctl apply -f
and not the
server config file…
server config instead and that gives me the same error
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 <https://fleet.corp.example.com>
should work for you. Let me know if you have any further issues.