Kubernetes error - 1.12.2 - Failed to upload file

[thirumalaicb]

Actual Behavior

Error Starting Kubernetes
Error: /Applications/Rancher Desktop.app/Contents/Resources/resources/darwin/lima/bin/limactl.ventura exited with code 1
Last command run:
/Applications/Rancher Desktop.app/Contents/Resources/resources/darwin/lima/bin/limactl.ventura copy /var/folders/hv/mbh2qgjj3vsdl61d9x99y1yr0000gp/T/rd-nginx.conf-ycIAMt/nginx.conf 0:/tmp/rd-nginx.conf-ycIAMt.nginx.conf

Context:
Configuring image proxy

Some recent logfile lines:
'/var/folders/hv/mbh2qgjj3vsdl61d9x99y1yr0000gp/T/rd-nginx.conf-ycIAMt/nginx.conf',
'0:/tmp/rd-nginx.conf-ycIAMt.nginx.conf'
],
stdout: '',
stderr: '/usr/bin/scp: write remote "/tmp/rd-nginx.conf-ycIAMt.nginx.conf": Failure\r\n' +
'/usr/bin/scp: failed to upload file /var/folders/hv/mbh2qgjj3vsdl61d9x99y1yr0000gp/T/rd-nginx.conf-ycIAMt/nginx.conf to /tmp/rd-nginx.conf-ycIAMt.nginx.conf\r\n',
code: 1,
[Symbol(child-process.command)]: '/Applications/Rancher Desktop.app/Contents/Resources/resources/darwin/lima/bin/limactl.ventura copy /var/folders/hv/mbh2qgjj3vsdl61d9x99y1yr0000gp/T/rd-nginx.conf-ycIAMt/nginx.conf 0:/tmp/rd-nginx.conf-ycIAMt.nginx.conf'
}
lima.ha.stderr.log
lima.log

Steps to Reproduce

I had to restart my computer and after restarting,

• Start Rancher Desktop
• Provide admin rights when prompted.
• When the status indicates "Installing CA certificates...", an error is displayed.

Result

Could not start Docker containers.

Expected Behavior

Docker containers should start.

Additional Information

This is happening all of a sudden. FYI, I usually keep my MacOS libraries updated by running brew upgrade. Maybe some library seems incompatible?

I have Kubernetes disabled. Even when enabling it has no difference.

Rancher Desktop Version

1.11.1

Rancher Desktop K8s Version

K8S disabled

Which container engine are you using?

moby (docker cli)

What operating system are you using?

macOS

Operating System / Build Version

Sonoma 14.1.1 (23B81)

What CPU architecture are you using?

x64

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

None

Windows User Only

No response

[slali-dev]

Hi @thirumalaicb
Did this start raising after system update?
I'm facing the same issue here with the same system, and it happened right after I upgraded to Sonoma 14.2.1

[thirumalaicb]

Hi @thirumalaicb Did this start raising after system update? I'm facing the same issue here with the same system, and it happened right after I upgraded to Sonoma 14.2.1

@slali-dev I am not sure if it is after upgrade. I suspect it to be the one I mentioned in Additional Information. But I could be wrong.

[thirumalaicb]

@jandubois any advice here please?

[chimico]

Using:

• macOS 14.3
• Rancher Desktop 1.12.1
• Kubernetes turned off.

Using the Reset Kubernetes worked.

[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.

@thirumalaicb included 2 log files, and the OS info, but unfortunately the other log files are still needed.

For the others that reply with "I have the same problem", that is not helpful, as the only common thing I get from this is that Rancher Desktop also doesn't start for you. But it is impossible to tell if this happens for the same reasons as the original issue creator. We need your log files and setup information as well!

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.

[thirumalaicb]

@jandubois Please find attached. Thank you for looking into this.
rancher-logs.zip

I also tried upgrading to 1.12.0 and then to 1.12.2 today and still the same issue. The OS version is now Sonoma 14.2.1.

[anderson-marques]

For me solved by reseting setting to Factory, upgrating Rancher Desktop and Kubernetes version.

[thirumalaicb]

Thank you @anderson-marques. That worked for me as well. Back to running Docker once again.
OS: Sonoma 14.3 (23D56)
Rancher: 12.2 still

[stampycode]

I had this same issue running on Windows 10, multiple times. My suspicion is that it occurs when Rancher doesn't have access to the internet, as this machine mostly runs without internet access.

Solution for us that has always worked:

- Shut down Rancher desktop
- open terminal
- wsl --unregister rancher-desktop
- start Rancher desktop