I ve been using dagster serverless for a while and it s work

Question

I ve been using dagster serverless for a while and it s working great I haven t developed locally in a while but I ve now I m running into a problem Even without any changes to the code that is running in dagster serverless every job I try to run locally eventually raises this error ```Multiprocess executor child process for step was terminated by signal 7 SIGBUS dagster core executor child process executor ChildProcessCrashException``` The error comes up at different times in the pipeline but it happens within 2 minutes every time I m running dagit in a container on an M1 Mac I ve assigned 8GB memory to docker and it doesn t look like I m getting at all close to the memory limit I m a bit stumped here

Sterling Paramore · Answer

Well shoot I took my docker files and ran everything on an Intel Mac and it works flawlessly

Sterling Paramore · Answer

I tried forcing ` platform=linux amd86` but I was getting some bizarre errors about it not being able to load the python regex library Looks like there might be some changes to MacOS 13 rosetta in docker for desktop that could have some effect so I m going to try upgrading from 12 to 13 and try again

Sterling Paramore · Answer

Upgrading to MacOS 13 and enabling the experimental features did not resolve the issue with the SIGBUS error

Sterling Paramore · Answer

Strangely this helped somewhat It reduced the issue to sometimes rather than every time <https stackoverflow com questions 66640705 how can i install grpcio on an apple m1 silicon laptop 68137855 68137855>

Sterling Paramore · Answer

FOUND THE ISSUE I had switched my Docker for Desktop to use VirtioFS This sped up some builds but ultimately caused this issue Switching back to gRPC FUSE make this error go away