https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# rancher-desktop
a
This message was deleted.
w
I'm sorry for being late for reply. Thank you for your reactions! @proud-jewelry-46860
Note that that error message (about 
limit
) is a red herring; it's because the WSL kernel doesn't support something, but it usually seems to be able to limp along.  There may be a different error somewhere else in the logs.
I thought 
limit
message was the cause of the problem, but in fact there are a lot of other error or warning messages. I attach the whole 
k3s.log
file. Could you find what the real problem is...? Thanks!
Thank you for response. I noticed I missed telling you some of the most important information. • The problem is I can't connect to docker daemon after starting up Rancher Desktop, from both WSL and Windows command prompt. Both messages indicate docker daemon might not be running. • No messages can be seen on the bottom left side of Rancher Desktop screen. • In 
background.log
, logged a lot of NUL chars(U+0000), followed by the message below; the log file has only one line. 
2022-02-24T01:55:10.067Z: event settings-read in main: [object Object]
If you need more information, please tell me about that.
just packing up all of the logs in a zip file might help
I attach all the log files.
Open in Slack
PreviousNext
Powered by