Cluster don't start at boot

The cluster start is failed on boot. Maybe we are missing a service dep (containerd .. or something like that)

● k3d@eole3.service
     Loaded: loaded (/etc/systemd/system/k3d@.service; enabled; vendor preset: enabled)
     Active: failed (Result: exit-code) since Tue 2022-02-15 12:04:11 UTC; 22s ago
    Process: 1777 ExecStart=/usr/local/bin/k3d cluster start eole3 (code=exited, status=1/FAILURE)
   Main PID: 1777 (code=exited, status=1/FAILURE)

Feb 15 12:03:50 ubt2004 k3d[1777]: INFO[0000] Starting Node 'k3d-eole3-server-0'
Feb 15 12:03:56 ubt2004 k3d[1777]: INFO[0006] Starting agents...
Feb 15 12:03:56 ubt2004 k3d[1777]: INFO[0006] Starting Node 'k3d-eole3-agent-1'
Feb 15 12:03:57 ubt2004 k3d[1777]: INFO[0006] Starting Node 'k3d-eole3-agent-2'
Feb 15 12:03:57 ubt2004 k3d[1777]: INFO[0006] Starting Node 'k3d-eole3-agent-0'
Feb 15 12:04:11 ubt2004 k3d[1777]: INFO[0020] Starting helpers...
Feb 15 12:04:11 ubt2004 k3d[1777]: FATA[0020] Failed to add one or more helper nodes: runtime failed to start node 'k3d-eole3-tools': failed to get container for node 'k3d-eole3-tools': Didn't find container for>
Feb 15 12:04:11 ubt2004 systemd[1]: k3d@eole3.service: Main process exited, code=exited, status=1/FAILURE
Feb 15 12:04:11 ubt2004 systemd[1]: k3d@eole3.service: Failed with result 'exit-code'.
Feb 15 12:04:11 ubt2004 systemd[1]: Failed to start k3d@eole3.service.
...skipping...