Alexander Sperling

Hej, I'm interested in that. However, I did some backend work in python, mainly shifting data back and forth, so this might take some longer time. If this is acceptable...

they now updated the version to 20.9.0, but this wont fix the CVE either...

I wonder if it should work with node `20.12.1` since this is the version which is defined in the `.nvmrc` https://github.com/microsoft/vscode/blob/main/.nvmrc You know why there are differences with the .yarnrc...

> The field needs to be propagated to the generated Alertmanager configuration. Is this something I have to trigger via make or do I still miss some code for that...

@simonpasquier got some time and took a look into this again could you check if this is fine now or if I still miss something?

Upgrading the node Version in the `FROM` section of the Dockerfile helps. eg. `FROM node:17.1.0` --> `FROM node:18` however, when doing this you might also need to adapt the command...

@code-asher they now updated to 20.11.1 and so did I 😄

```bash pi@xandar:~ $ uname -a Linux xandar 6.6.74+rpt-rpi-v8 #1 SMP PREEMPT Debian 1:6.6.74-1+rpt1 (2025-01-27) aarch64 GNU/Linux ```

Thanks for the quick answer, Will try to change this. And we are using 5.10

Tried to change the volume mounts and now I'm getting the following error. ``` Error: failed to create containerd task: failed to create shim task: OCI runtime create failed: runc...