gpilleux

Just downloaded the 4.19.56-surface-linux-surface kernel version and still having the same problem.... Could this be a problem with my distro? I'm running Ubuntu 19.10 `> uname -a Linux matrix 4.19.56-surface-linux-surface...

Hi Fluder, thanks for answering. I commented out the lines you showed in the next.config.js file and the gui container is answering with the same `segmentation fault` log as shown...

I am using the Pinecone free plan and thanks to [this issue](https://github.com/TransformerOptimus/SuperAGI/issues/200) I managed to setup the workaround for it. Now the gui container is not showing `segmentation fault` but...

I left all 4 containers running and after a while I tried to restart the gui container and `segmentation fault` is back 😢 ``` 2023-06-06 12:01:06 superagi-gui-1 | 2023-06-06 12:01:06...

All the executions have been with the latest main (except this one time with the release verison 0.0.2). I have pulled the latest main branch and still getting `Segmentation Fault`...

So I ran a bash shell on the container and you can see that npm is installed and up to date. Segmentation fault visible after second `npm run dev` command....

I have those exact same settings on the Docker Desktop. Since I don't know how else to debug this, I deleted the project and cloned the repo from scratch. Only...

Now I cloned the repo on an ubuntu machine and the gui is running fine! I'm really confused as to why this isn't working on my macOS... but oh well,...

This actually solves it. So much thanks @kcverde !!

I tried many combinations of settings of IPs and couldn't get it working and actually got a bit confused. When I execute `ifconfig` I get many bridges on different IP...