not starting correctly with yamlint about addon-vscode

[gnkarn]

it may be a memory problem, i asigning the VM 2GB, and when open this addon it goes to 90% , and next it hangs the machine . So reboot and uninstall is the only cure for now .

[frenck]

@gnkarn Sorry I'm lost on what you are doing here. Please share the config you are trying to startup.
Secondly, the question remains the same as in #13 (and I'm unsure why you'd create another issue instead of just continuing on the existing one?):

Why are you trying to install yamllint? Since it is installed already! (pre-built, shipped with the add-on).

[michaelblight]

I'm having the same problem. I did the following:

1. Installed the add-on.
2. Turned off SSL in the config.
3. Put a password in the config (it then removes it after you save?).
4. Started the add-on.
5. Checked the logs. It ends with INFO Connected to shared process, no errors apparent.
6. Clicked on "Open Web UI". First time it asked for my HA credentials. Welcome page displayed (no prompt for password saved in config?).
7. Clicked on "configuration.yaml". Pretty much the whole VM seemed to hang, including containers not linked to hassio (eg. Portainer, PiHole). After several unintalls/re-installs, it seemed to work once very slowly, but then selecting another file caused it to hang. I had to power cycle to get it going again.

My config is:

{
  "ssl": false,
  "certfile": "fullchain.pem",
  "keyfile": "privkey.pem",
  "packages": [],
  "init_commands": []
}

It included "password", but every time I save and return to the screen it is gone.

[frenck]

@michaelblight your report is not related at all. Password methods has changed in the last release. Please login using your username password from Home Assistant. The password option on the add-on has been removed.

@gnkarn Are you getting back on my question? Or can this be closed?

[gnkarn]

just installing as per the docs,

config : {
"log_level": "info",
"ssl": false,
"certfile": "fullchain.pem",
"keyfile": "privkey.pem",
"packages": [
"mariadb-client"
],
"init_commands": [
"pip3 install yamllint"
]
}

, as i say , this could be that VSC is taking too much memory from the Virtual Machine, and resources are not enough .

You can close this , i will continue to use VSC , from the main computer for now , thanks a ton .

[frenck]

That is just an example which as a big note right next to it: DO NOT USE.
you do not need to install yamllint, since it is already installed by default. The example just shows HOW you could use the init_commands option.

[addons-assistant]

This thread has been automatically locked because it has not had recent activity. Please open a new issue for related bugs and link to relevant comments in this thread.