Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Extension fails to start #90

Closed
ghost opened this issue Feb 13, 2020 · 0 comments · Fixed by #91
Closed

Extension fails to start #90

ghost opened this issue Feb 13, 2020 · 0 comments · Fixed by #91
Assignees
Labels
bug Something isn't working

Comments

@ghost
Copy link

ghost commented Feb 13, 2020

Describe the bug
Extension fails to start after installing for the first time

To Reproduce
Steps to reproduce the behavior:

  1. Installed extension.
  2. Re-opened VSCode.
  3. Try to run any of the Okteto ... commands, and get an error.

Expected behavior
The extension should start :)

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):
VSCode details:

Version: 1.41.1
Commit: 26076a4de974ead31f97692a0d32f90d735645c0
Date: 2019-12-18T15:04:31.999Z
Electron: 6.1.5
Chrome: 76.0.3809.146
Node.js: 12.4.0
V8: 7.6.303.31-electron.0
OS: Linux x64 4.19.0-6-amd64

Smartphone (please complete the following information):

  • Device: [e.g. iPhone6]
  • OS: [e.g. iOS8.1]
  • Browser [e.g. stock browser, safari]
  • Version [e.g. 22]

Additional context

[2020-02-13 14:56:51.510] [exthost] [error] Activating extension Okteto.remote-kubernetes failed due to an error:
[2020-02-13 14:56:51.510] [exthost] [error] Error: Command failed with exit code 2 (ENOENT): ( cat /var/lib/dbus/machine-id /etc/machine-id 2> /dev/null || hostname ) | head -n 1 || :
spawnSync ( ENOENT
	at Object.spawnSync (internal/child_process.js:1041:20)
	at Object.spawnSync (child_process.js:615:24)
	at Function.e.exports.sync (/home/abecker/.vscode/extensions/okteto.remote-kubernetes-0.1.18/dist/extension.js:137:36038)
	at Function.e.exports.commandSync (/home/abecker/.vscode/extensions/okteto.remote-kubernetes-0.1.18/dist/extension.js:137:36726)
	at Object.t.protect (/home/abecker/.vscode/extensions/okteto.remote-kubernetes-0.1.18/dist/extension.js:310:73269)
	at Object.t.getOktetoId (/home/abecker/.vscode/extensions/okteto.remote-kubernetes-0.1.18/dist/extension.js:310:55876)
	at t.activate (/home/abecker/.vscode/extensions/okteto.remote-kubernetes-0.1.18/dist/extension.js:310:8718)
	at Function._callActivateOptional (/usr/share/code/resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:695:911)
	at Function._callActivate (/usr/share/code/resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:695:562)
	at /usr/share/code/resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:694:651
	at async Promise.all (index 0)
@rberrelleza rberrelleza added the bug Something isn't working label Feb 14, 2020
@rberrelleza rberrelleza self-assigned this Feb 14, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant