After switching to ` op` and ` graph` my GRPC server in stag

Question

After switching to ` op` and ` graph` my GRPC server in staging box no longer works ```OSError Errno 30 Read only file system export content lid apps dagster web File export content lid apps meeseeks backend dagster grpc server i001 libexec meeseeks backend 015263caabc6969a26157a73f5dcbb71f6e53ea18d1e4d986685ee6b374c9871 site packages dagster core execution plan execute plan py line 193 in dagster event sequence for step for step event in check generator step events File export content lid apps meeseeks backend dagster grpc server i001 libexec meeseeks backend 015263caabc6969a26157a73f5dcbb71f6e53ea18d1e4d986685ee6b374c9871 site packages dagster core execution plan execute step py line 326 in core dagster event sequence for step for evt in type check and store output step context user event input lineage File export content lid apps meeseeks backend dagster grpc server i001 libexec meeseeks backend 015263caabc6969a26157a73f5dcbb71f6e53ea18d1e4d986685ee6b374c9871 site packages dagster core execution plan execute step py line 380 in type check and store output for evt in store output step context step output handle output input lineage File export content lid apps meeseeks backend dagster grpc server i001 libexec meeseeks backend 015263caabc6969a26157a73f5dcbb71f6e53ea18d1e4d986685ee6b374c9871 site packages dagster core execution plan execute step py line 490 in store output handle output res = output manager handle output output context output value File export content lid apps meeseeks backend dagster grpc server i001 libexec meeseeks backend 015263caabc6969a26157a73f5dcbb71f6e53ea18d1e4d986685ee6b374c9871 site packages dagster core storage fs io manager py line 119 in handle output mkdir p os path dirname filepath File export content lid apps meeseeks backend dagster grpc server i001 libexec meeseeks backend 015263caabc6969a26157a73f5dcbb71f6e53ea18d1e4d986685ee6b374c9871 site packages dagster utils init py line 150 in mkdir p os makedirs path File export apps python 3 7 lib python3 7 os py line 213 in makedirs makedirs head exist ok=exist ok File export apps python 3 7 lib python3 7 os py line 213 in makedirs makedirs head exist ok=exist ok File export apps python 3 7 lib python3 7 os py line 213 in makedirs makedirs head exist ok=exist ok Previous line repeated 4 more times File export apps python 3 7 lib python3 7 os py line 223 in makedirs mkdir name mode ```

Xu Zhang · Answer

< sandy> sorry to ping you directly i really need some help here I m leading my team to convert our stuff onto Dagster but it just gave too many issues today

Xu Zhang · Answer

` export content lid apps dagster web` is the HOME of the Dagit which is on host `A` the grpc server is running on the host `B` which only has the access to ` export content lid apps meeseeks backend dagster grpc server` and it was trying to create a folder under `dagster web` which it does not have access to < daniel> helped me previously by asking me to remove the local compute log manager thus I switched to `NoOpComputeLogManager` which works perfectly I have no idea why switching from ` solid` to ` op` would causing grpc server to behave differently

sandy · Answer

I have a guess about what s going on here The new APIs include a change to the default IO manager it now defaults to the filesystem IO manager instead of the memory IO manager which allows re execution and multiprocess execution to work by default

chris · Answer

^

sandy · Answer

It will try to store using whatever base directory is specified in your dagster yaml

Xu Zhang · Answer

how do i change it back to the in memory IO manager

Xu Zhang · Answer

```resource defs Optional Dict str ResourceDefinition Resources that are required by this graph for execution If not defined io manager will default to filesystem ```

sandy · Answer

Instead of including your graph directly in the repo you can include `<http my graph to|my graph to> job resource defs= io manager mem io manager executor def=in process executor `

Xu Zhang · Answer

thank you sandy

Xu Zhang · Answer

worked with `<http my graph to|my graph to> job resource defs= io manager mem io manager executor def=in process executor ``

sandy · Answer

that is great to hear