Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

RD failed to start with version 1.1.0 or 1.1.1

See original GitHub issue

Actual Behavior

RD failed to start after upgrade from 1.0.0/1.0.1 or clean install with version 1.1.0 or 1.1.1.

Steps to Reproduce

Scenario 1: From version 1.0.0 or 1.0.1 working on my PC with auto update activated, after new version download and RD restart, RD fail to start.

Scenario 2: After uninstall and clean all rancher-desktop directories, clean install with 1.1.0 or 1.1.1 produce same problem, RD fail to start with below error log

Result

background.log

2022-03-06T22:05:01.902Z: Error starting up: <ref *1> Error: spawnSync C:\Users\myname.MYCOMPANY-EMEA\AppData\Local\Programs\Rancher Desktop\resources\app.asar.unpacked\node_modules\win-ca\lib\roots.exe ENOBUFS
    at Object.spawnSync (node:internal/child_process:1083:20)
    at spawnSync (node:child_process:821:24)
    at Object.execFileSync (node:child_process:867:15)
    at Object.func [as execFileSync] (node:electron/js2c/asar_bundle:5:2027)
    at Object.run (C:\Users\myname.MYCOMPANY-EMEA\AppData\Local\Programs\Rancher Desktop\resources\app.asar\node_modules\win-ca\lib\fallback.js:43:26)
    at api (C:\Users\myname.MYCOMPANY-EMEA\AppData\Local\Programs\Rancher Desktop\resources\app.asar\node_modules\win-ca\lib\index.js:60:10)
    at C:\Users\myname.MYCOMPANY-EMEA\AppData\Local\Programs\Rancher Desktop\resources\app.asar\dist\app\background.js:29:161624
    at C:\Users\myname.MYCOMPANY-EMEA\AppData\Local\Programs\Rancher Desktop\resources\app.asar\dist\app\background.js:29:162210 {
  errno: -4060,
  code: 'ENOBUFS',
  syscall: 'spawnSync C:\\Users\\myname.MYCOMPANY-EMEA\\AppData\\Local\\Programs\\Rancher Desktop\\resources\\app.asar.unpacked\\node_modules\\win-ca\\lib\\roots.exe',
  path: 'C:\\Users\\myname.MYCOMPANY-EMEA\\AppData\\Local\\Programs\\Rancher Desktop\\resources\\app.asar.unpacked\\node_modules\\win-ca\\lib\\roots.exe',
  spawnargs: [ 'root', 'ca' ],
  error: [Circular *1],
  status: null,
  signal: 'SIGTERM',
  output: [
    null,
    <Buffer 33 30 38 32 30 36 31 61 33 30 38 32 30 34 30 32 61 30 30 33 30 32 30 31 30 32 30 32 31 32 31 31 32 30 32 30 63 38 34 66 37 35 33 36 62 62 61 65 38 39 ... 1049151 more bytes>,
    <Buffer >
  ],
  pid: 22072,
  stdout: <Buffer 33 30 38 32 30 36 31 61 33 30 38 32 30 34 30 32 61 30 30 33 30 32 30 31 30 32 30 32 31 32 31 31 32 30 32 30 63 38 34 66 37 35 33 36 62 62 61 65 38 39 ... 1049151 more bytes>,
  stderr: <Buffer >
}

Expected Behavior

Have RD running

Additional Information

No response

Rancher Desktop Version

1.1.1

Rancher Desktop K8s Version

1.22.7

Which container runtime are you using?

containerd (nerdctl)

What operating system are you using?

Windows

Operating System / Build Version

Windows 10 Enterprise 21H2

What CPU architecture are you using?

x64

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

No response

Windows User Only

VPN PulseSecure but not connected during the test/problem No other specific rules, but my PC is managed by my company

Not that Rancher Desktop version 1.0.0 or 1.0.1 is working on my PC after uninstall 1.1.1

Edited by @mook-as: formatting.

Issue Analytics

State:
Created 2 years ago
Comments:11 (8 by maintainers)

Top GitHub Comments

1reaction

boks21commented, Mar 8, 2022

Already exists a solution for this issue? I have the same problem after upgrade do 1.1.1 Version 1.0.1 was working fine

2022-03-08T12:05:42.212Z: Error starting up: <ref *1> Error: spawnSync C:\Users\myuser\AppData\Local\Programs\Rancher Desktop\resources\app.asar.unpacked\node_modules\win-ca\lib\roots.exe ENOBUFS at Object.spawnSync (node:internal/child_process:1083:20) at spawnSync (node:child_process:821:24) at Object.execFileSync (node:child_process:867:15) at Object.func [as execFileSync] (node:electron/js2c/asar_bundle:5:2027) at Object.run (C:\Users\myuser\AppData\Local\Programs\Rancher Desktop\resources\app.asar\node_modules\win-ca\lib\fallback.js:43:26) at api (C:\Users\myuser\AppData\Local\Programs\Rancher Desktop\resources\app.asar\node_modules\win-ca\lib\index.js:60:10) at C:\Users\myuser\AppData\Local\Programs\Rancher Desktop\resources\app.asar\dist\app\background.js:29:161624 at C:\Users\myuser\AppData\Local\Programs\Rancher Desktop\resources\app.asar\dist\app\background.js:29:162210 { errno: -4060, code: 'ENOBUFS', syscall: 'spawnSync C:\\Users\\myuser\\AppData\\Local\\Programs\\Rancher Desktop\\resources\\app.asar.unpacked\\node_modules\\win-ca\\lib\\roots.exe', path: 'C:\\Users\\myuser\\AppData\\Local\\Programs\\Rancher Desktop\\resources\\app.asar.unpacked\\node_modules\\win-ca\\lib\\roots.exe', spawnargs: [ 'root', 'ca' ], error: [Circular *1], status: null, signal: 'SIGTERM', output: [ null, <Buffer 33 30 38 32 30 36 35 35 33 30 38 32 30 34 33 64 61 30 30 33 30 32 30 31 30 32 30 32 30 34 37 36 32 39 30 37 65 33 33 30 30 64 30 36 30 39 32 61 38 36 ... 1048922 more bytes>, <Buffer > ], pid: 16836, stdout: <Buffer 33 30 38 32 30 36 35 35 33 30 38 32 30 34 33 64 61 30 30 33 30 32 30 31 30 32 30 32 30 34 37 36 32 39 30 37 65 33 33 30 30 64 30 36 30 39 32 61 38 36 ... 1048922 more bytes>, stderr: <Buffer > }

0reactions

ChBerrichcommented, Mar 29, 2022

Ok, thanks for the quick update ! Sorry I open a new issue #1927 as I was not sure that my comment on closed issue will be view So I wait your next update