https://flyte.org logo
#ask-the-community
Demo cluster in Windows
# ask-the-community
c

chronoclast

04/02/2024, 12:31 PM
Hi fellow flyers :) Trying to make a demo cluster work in a Windows machine. I was able to install
flytectl
, both manually downloading the executable, and also using Git Bash. After that I run for example:
powershell Copy code
.\flytectl.exe demo start --force
The container boots up normally:
Copy code
time="2024-04-02T13:33:14+02:00" level=info msg="[0] Couldn't find a config file []. Relying on env vars and pflags."
šŸ§‘ā€šŸ­ Bootstrapping a brand new Flyte cluster... šŸ”Ø šŸ”§
šŸ‹ Going to use Flyte v1.11.0 release with image cr.flyte.org/flyteorg/flyte-sandbox-bundled:sha-db1182142e473836f47fa3a8b376a10fc6ef8386
šŸ§‘ā€šŸ­ Starting container... šŸ”Ø šŸ”§
ā³ Waiting for cluster to come up... ā³
Unfortunately, after a long wait it crashes with the following error:
Copy code
Error: All attempts fail:
#1: Get "https://127.0.0.1:6443/livez": x509: certificate signed by unknown authority - error from a previous attempt: EOF
#2: Get "https://127.0.0.1:6443/livez": x509: certificate signed by unknown authority
...
#15: Get "https://127.0.0.1:6443/livez": x509: certificate signed by unknown authority
{"json":{},"level":"error","msg":"All attempts fail:\n#1: Get \"https://127.0.0.1:6443/livez\": x509: certificate signed by unknown authority - error from a previous attempt: EOF\n#2: Get \"https://127.0.0.1:6443/livez\": x509: certificate signed by unknown authority\n#3: ...
...
... Get \"https://127.0.0.1:6443/livez\": x509: certificate signed by unknown authority","ts":"2024-04-02T14:00:39+02:00"}
I checked the logs of the pod, and it seems to be retrying these instructions a few times before the crash:
Copy code
W0402 11:58:30.856895      63 sysinfo.go:203] Nodes topology is not available, providing CPU topology
E0402 11:58:30.864314      63 info.go:114] Failed to get system UUID: open /etc/machine-id: no such file or directory
W0402 11:58:30.865241      63 info.go:53] Couldn't collect info from any of the files in "/etc/machine-id,/var/lib/dbus/machine-id"
I0402 11:58:30.865403      63 container_manager_linux.go:848] "CPUAccounting not enabled for process" pid=63
I0402 11:58:30.865431      63 container_manager_linux.go:851] "MemoryAccounting not enabled for process" pid=63
I'm using the default configuration, Rancher desktop (i.e. all
docker
commands are operative) and
kubectl
is installed and working. Any idea of what I'm doing wrong? Thanks a lot! :D
8 Views