`talosctl cluster create docker` fails on Fedora 44

[Chaz6]

Bug Report

Description

I would like to create a local cluster as per the quickstart guide on my host running Fedora 44, but each time I try it fails with 3 errors.

Logs

talosctl cluster create docker
generating PKI and tokens
creating state directory in "/home/chaz/.talos/clusters/talos-default"
creating network talos-default
creating controlplane nodes
creating worker nodes
renamed talosconfig context "talos-default" -> "talos-default-1"
waiting for Talos API (to bootstrap the cluster)
bootstrap error: 3 error(s) occurred:
        rpc error: code = DeadlineExceeded desc = context deadline exceeded while waiting for connections to become ready
        rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing: dial tcp 127.0.0.1:45843: i/o timeout"
        timeout

Environment

• Talos version: v1.13.4-707dbd89
• Kubernetes version: v1.36.2
• Platform: amd64

[smira]

The i/o timeout points towards something with exposing Docker container's pods to the host.

But in the end this command doesn't do anything more than creating docker containers, so you can inspect docker state to see what's wrong.

Also on Linux, talosctl cluster create qemu is much for fun/value to try out Talos ;)

[Chaz6]

The docker containers seem to have been created:-

docker ps -a
CONTAINER ID   IMAGE                              COMMAND        CREATED          STATUS          PORTS                                                   NAMES
7a557b8f666c   ghcr.io/siderolabs/talos:v1.13.4   "/sbin/init"   48 minutes ago   Up 48 minutes                                                           talos-default-worker-1
91d13e12be67   ghcr.io/siderolabs/talos:v1.13.4   "/sbin/init"   48 minutes ago   Up 48 minutes   127.0.0.1:43463->6443/tcp, 127.0.0.1:42537->50000/tcp   talos-default-controlplane-1

Also:-

talosctl cluster show
PROVISIONER           docker
NAME                  talos-default
NETWORK NAME          talos-default
NETWORK CIDR          10.5.0.0/24
NETWORK GATEWAY       10.5.0.1
NETWORK MTU           1500
KUBERNETES ENDPOINT   https://127.0.0.1:43463

NODES:

NAME                           TYPE           IP         CPU    RAM      DISK
talos-default-controlplane-1   controlplane   10.5.0.2   2.00   2.1 GB   -
talos-default-worker-1         worker         10.5.0.3   2.00   2.1 GB   -

Is there anywhere else to look for issues?

[Chaz6]

From the controlplane container:-

[talos] task startAllServices (1/1): 2026/06/18 15:52:28 service "etcd" to be "up"
[talos] 2026/06/18 15:52:36 controller failed {"component": "controller-runtime", "controller": "k8s.KubeletStaticPodController", "error": "error refreshing pod status: error fetching pod status: an error on the server (\"Authorization error (user=apiserver-kubelet-client, verb=get, resource=nodes, subresource=pods)\") has prevented the request from succeeding"}

[smira]

127.0.0.1:45843: i/o timeout <- this is the exposed port of the first container (you can see that in the docker ps output)

but something is broken on your side that it doesn't work? (wild guess).

You can try hitting port 50000 on the container IP directly - if it works, but the exposed one doesn't you have something wrong with docker port exposing, or something else conflicting here.