Kubernetes Issue after upgrading to version 1.12.1

[gadafix]

Actual Behavior

When I open Rancher I immediately see the following message

Docker functionality isn't working.

Steps to Reproduce

Upgrade Rancher version to 1.12.1

Result

Expected Behavior

I expect Rancher to load docker and allow working with it in the command line.

Additional Information

No response

Rancher Desktop Version

1.12.1

Rancher Desktop K8s Version

v1.25.6

Which container engine are you using?

moby (docker cli)

What operating system are you using?

macOS

Operating System / Build Version

macOS Ventura 13.2.1 (22D68)

What CPU architecture are you using?

arm64 (Apple Silicon)

Linux only: what package format did you use to install Rancher Desktop?

None

Windows User Only

No response

[pgarrett-twc]

I had a similar error on startup on 1.11.1. Restarting a couple of times resolved the problem.

[srikanthtallapaneni]

I'm also facing the same issue, with both 1.11.1 and 1.12.1. Tried restarting, k8s reset, Factory reset, but nothing seem to be working. Docker functionality is still unavailable.

[abaerptc]

Same issue here with macOS x86_64. Reset and reinstall did not work. Downgraded to 1.11.1 and everything worked again.

[jandubois]

There is not much we can do unless the people affected provide the full set of log files, plus information about OS version, CPU arch, etc.

So please, if this is reproducible by you, collect all the logs in the log directory and attach them to a bug report or make them otherwise available.

[srikanthtallapaneni]

My issue is resolved

The problem was my username.
My initial mac username used to be 'srikanthtallapaneni***'. The problem with this was that Rancher was trying to execute some file when it is trying to start docker and eventually kubernetes. But combined with my username, that file path's length has become 117 where the allowed value for a path in mac(UNIX_MAX_PATH) is 110
ex: This is the path Rancher was trying to access
Users/srikanthtallapaneni****/Library/Application Support/rancher-desktop/lima/0/ssh.sock.1234567890123456 - which if observed has length 117 (limit is 110), so it was failing.
Then I went ahead(reset my mac) and renamed the user to a smaller one while setting up which brought the number of characters in the path within the limit and Rancher was able to execute/access the above file to do the background operations and hence installed successfully.