Hey team, I have been having a issue recently wher...
# flyte-support
b
Hey team, I have been having a issue recently where
flytectl demo start
repeatedly produces this error:
Copy code
flytectl demo start
šŸ§‘ā€šŸ­ Bootstrapping a brand new Flyte cluster... šŸ”Ø šŸ”§
šŸ‹ Going to use Flyte v1.16.1 release with image <http://cr.flyte.org/flyteorg/flyte-sandbox-bundled:sha-8b999cef8739bd3a117d9dd3b9a16b06493605bd|cr.flyte.org/flyteorg/flyte-sandbox-bundled:sha-8b999cef8739bd3a117d9dd3b9a16b06493605bd>
šŸ‹ Pulling image <http://cr.flyte.org/flyteorg/flyte-sandbox-bundled:sha-8b999cef8739bd3a117d9dd3b9a16b06493605bd|cr.flyte.org/flyteorg/flyte-sandbox-bundled:sha-8b999cef8739bd3a117d9dd3b9a16b06493605bd>
sha-8b999cef8739bd3a117d9dd3b9a16b06493605bd: Pulling from flyteorg/flyte-sandbox-bundled
52e0b83afc58: Pull complete
668cddf73609: Pull complete
c7e7273a9d9e: Pull complete
ff7dd37cdc54: Pull complete
9e34fcc4c01b: Pull complete
ce1037fe9e1d: Pull complete
e95b18ff6786: Pull complete
2a5fa435b225: Pull complete
Digest: sha256:26ed516df2aeadc7701d48ed0b8745ce033046e00b74e67555a11f20995a4271
Status: Downloaded newer image for <http://cr.flyte.org/flyteorg/flyte-sandbox-bundled:sha-8b999cef8739bd3a117d9dd3b9a16b06493605bd|cr.flyte.org/flyteorg/flyte-sandbox-bundled:sha-8b999cef8739bd3a117d9dd3b9a16b06493605bd>
šŸ§‘ā€šŸ­ Starting container... šŸ”Ø šŸ”§
ā³ Waiting for cluster to come up... ā³
Error: All attempts fail:
#1: Get "<https://127.0.0.1:6443/livez>": dial tcp 127.0.0.1:6443: connect: connection refused - error from a previous attempt: read tcp 127.0.0.1:56220->127.0.0.1:6443: read: connection reset by peer
#2: Get "<https://127.0.0.1:6443/livez>": dial tcp 127.0.0.1:6443: connect: connection refused
#3: Get "<https://127.0.0.1:6443/livez>": dial tcp 127.0.0.1:6443: connect: connection refused
#4: Get "<https://127.0.0.1:6443/livez>": dial tcp 127.0.0.1:6443: connect: connection refused
#5: Get "<https://127.0.0.1:6443/livez>": dial tcp 127.0.0.1:6443: connect: connection refused
#6: Get "<https://127.0.0.1:6443/livez>": dial tcp 127.0.0.1:6443: connect: connection refused
#7: Get "<https://127.0.0.1:6443/livez>": dial tcp 127.0.0.1:6443: connect: connection refused
#8: Get "<https://127.0.0.1:6443/livez>": dial tcp 127.0.0.1:6443: connect: connection refused
#9: Get "<https://127.0.0.1:6443/livez>": dial tcp 127.0.0.1:6443: connect: connection refused
#10: Get "<https://127.0.0.1:6443/livez>": dial tcp 127.0.0.1:6443: connect: connection refused
#11: Get "<https://127.0.0.1:6443/livez>": dial tcp 127.0.0.1:6443: connect: connection refused
#12: Get "<https://127.0.0.1:6443/livez>": dial tcp 127.0.0.1:6443: connect: connection refused
#13: Get "<https://127.0.0.1:6443/livez>": dial tcp 127.0.0.1:6443: connect: connection refused
#14: Get "<https://127.0.0.1:6443/livez>": dial tcp 127.0.0.1:6443: connect: connection refused
#15: Get "<https://127.0.0.1:6443/livez>": dial tcp 127.0.0.1:6443: connect: connection refused
{"json":{},"level":"error","msg":"All attempts fail:\n#1: Get \"<https://127.0.0.1:6443/livez>\": dial tcp 127.0.0.1:6443: connect: connection refused - error from a previous attempt: read tcp 127.0.0.1:56220->127.0.0.1:6443: read: connection reset by peer\n#2: Get \"<https://127.0.0.1:6443/livez>\": dial tcp 127.0.0.1:6443: connect: connection refused\n#3: Get \"<https://127.0.0.1:6443/livez>\": dial tcp 127.0.0.1:6443: connect: connection refused\n#4: Get \"<https://127.0.0.1:6443/livez>\": dial tcp 127.0.0.1:6443: connect: connection refused\n#5: Get \"<https://127.0.0.1:6443/livez>\": dial tcp 127.0.0.1:6443: connect: connection refused\n#6: Get \"<https://127.0.0.1:6443/livez>\": dial tcp 127.0.0.1:6443: connect: connection refused\n#7: Get \"<https://127.0.0.1:6443/livez>\": dial tcp 127.0.0.1:6443: connect: connection refused\n#8: Get \"<https://127.0.0.1:6443/livez>\": dial tcp 127.0.0.1:6443: connect: connection refused\n#9: Get \"<https://127.0.0.1:6443/livez>\": dial tcp 127.0.0.1:6443: connect: connection refused\n#10: Get \"<https://127.0.0.1:6443/livez>\": dial tcp 127.0.0.1:6443: connect: connection refused\n#11: Get \"<https://127.0.0.1:6443/livez>\": dial tcp 127.0.0.1:6443: connect: connection refused\n#12: Get \"<https://127.0.0.1:6443/livez>\": dial tcp 127.0.0.1:6443: connect: connection refused\n#13: Get \"<https://127.0.0.1:6443/livez>\": dial tcp 127.0.0.1:6443: connect: connection refused\n#14: Get \"<https://127.0.0.1:6443/livez>\": dial tcp 127.0.0.1:6443: connect: connection refused\n#15: Get \"<https://127.0.0.1:6443/livez>\": dial tcp 127.0.0.1:6443: connect: connection refused","ts":"2025-10-07T13:19:18-06:00"}
My
config-sandbox.yaml
contains this:
Copy code
admin:
  # For GRPC endpoints you might want to use dns:///flyte.myexample.com
  endpoint: dns:///localhost:30080
  insecure: true
My docker and flytectl versions are shown below:
Copy code
docker version
Client: Docker Engine - Community
 Version:           28.5.0
 API version:       1.51
 Go version:        go1.24.7
 Git commit:        887030f
 Built:             Thu Oct  2 14:54:28 2025
 OS/Arch:           linux/amd64
 Context:           default

Server: Docker Engine - Community
 Engine:
  Version:          28.5.0
  API version:      1.51 (minimum version 1.24)
  Go version:       go1.24.7
  Git commit:       cd04830
  Built:            Thu Oct  2 14:54:28 2025
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          v1.7.28
  GitCommit:        b98a3aace656320842a23f4a392a33f46af97866
 runc:
  Version:          1.3.0
  GitCommit:        v1.3.0-0-g4ca628d1
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0
and flytectl:
Copy code
{
  "App": "flytectl",
  "Build": "f2a1ad7d4",
  "Version": "0.9.5",
  "BuildTime": "2025-10-07 13:30:45.459309309 -0600 MDT m=+0.000898025"
Are there any suggestions anyone can provide to fix this? Also LMK if you need any other information.
Problem solved, I was pulling an image that's incompatible with my machine
e
Hi @bumpy-ambulance-52702 We fixed this, do you mind retrying
flytectl demo start
again?
šŸš€ 1
it should now get the compatible image
b
Yup, just tried it and it works now. Thank you!
šŸ™Œ 1