Shawn Maddock
09/16/2022, 7:40 PMfleetctl setup
documentation and help text says it takes a --config
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?Shawn Maddock
09/16/2022, 7:44 PMfleetctl
and not the fleet
server config file…Shawn Maddock
09/16/2022, 7:46 PMfleet
server config instead and that gives me the same errorMichal Nicpon
09/19/2022, 4:39 PMfleetctl
will use a config file located at ~/.fleet/config
. 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>
After that, fleetctl setup
should work for you. Let me know if you have any further issues.Michal Nicpon
09/19/2022, 4:40 PM