I have a really strange one. I'm hosting fleet in ...
# fleet
j
I have a really strange one. I'm hosting fleet in a pod in my kube cluster, with managed redis/mysql. Works great. We're using a flask app to basically call the fleet server to do fleet things, and it's been working fine. The issue I have is with the installers. Since its all linux images, and I can't really docker-in-docker to get pkg and msi, i'm trying to find some workout. I could maybe just have a pet VM with a service wrapped around it, the flask app would call the service, it would build it, and them dump it in a storage bucket in our cloud. Alternatively I did see that the containers with the tools for building these are also hosted -
bomutil/wix
- could I just host those pods and somehow build through them? Even with other tools (elastic), I haven't seen a really easy way for me to just grab an installer to give to someone
l
Hi! You can use
fleetdm/fleetctl
Docker image and generate packages the same way as using the
fleetctl
executable. E.g.
Copy code
docker run -v "$(pwd):/build" fleetdm/fleetctl:latest package --type pkg --enroll-secret=foo --fleet-url=<https://localhost:8080>
j
And this would have everything on it already
Ok this has potential, thank you
I'd probably still need to sit this on a VM though no?
Copy code
Error: initialize updates: failed to update metadata: update metadata: tuf: failed to decode root.json: expired at 2024-10-06 17:47:49 +0000 UTC
Weird timing? Am I missing anything?
l
Hi @Jan Jedrasik! This is an ongoing issue and we are working to fix it ASAP (#22687)