Hello all I m trying to spin up a PoC for my company I start

Question

Hello all I m trying to spin up a PoC for my company I started my project from the example project deploy docker and adapted only two files repo py and Dockerfile user code When I try to spin up the docker compose stack I got an grpc error which is saying that the user code server cannot be reached stack trace in thread In my repo I try to make a connection to a sql server database with sqlalchemy and Pyodbc I have therefore my dockerfile user code adapted to the following see thread Can someone please help me to solve this issue Thank you very much for your help

Joris Ganne · Answer

Stack trace usr local lib python3 7 site packages dagster core workspace context py 586 UserWarning Error loading repository location example user code dagster core errors DagsterUserCodeUnreachableError Could not reach user code server gRPC Error code UNAVAILABLE docker example dagit | docker example dagit | Stack Trace docker example dagit | File usr local lib python3 7 site packages dagster core workspace context py line 581 in load location docker example dagit | location = self create location from origin origin docker example dagit | File usr local lib python3 7 site packages dagster core workspace context py line 501 in create location from origin docker example dagit | return origin create location docker example dagit | File usr local lib python3 7 site packages dagster core host representation origin py line 331 in create location docker example dagit | return GrpcServerRepositoryLocation self docker example dagit | File usr local lib python3 7 site packages dagster core host representation repository location py line 575 in init docker example dagit | list repositories response = sync list repositories grpc self client docker example dagit | File usr local lib python3 7 site packages dagster api list repositories py line 19 in sync list repositories grpc docker example dagit | api client list repositories docker example dagit | File usr local lib python3 7 site packages dagster grpc client py line 230 in list repositories docker example dagit | res = self query ListRepositories api pb2 ListRepositoriesRequest docker example dagit | File usr local lib python3 7 site packages dagster grpc client py line 157 in query docker example dagit | e timeout=timeout custom timeout message=custom timeout message docker example dagit | File usr local lib python3 7 site packages dagster grpc client py line 141 in raise grpc exception docker example dagit | from e docker example dagit | docker example dagit | The above exception was caused by the following exception docker example dagit | grpc channel InactiveRpcError lt InactiveRpcError of RPC that terminated with docker example dagit | status = StatusCode UNAVAILABLE docker example dagit | details = failed to connect to all addresses docker example dagit | debug error string = created 1674117761 666041800 description Failed to pick subchannel file src core ext filters client channel client channel cc file line 3260 referenced errors created 1674117761 666041200 description failed to connect to all addresses file src core lib transport error utils cc file line 167 grpc status 14 docker example dagit | gt docker example dagit | docker example dagit | Stack Trace docker example dagit | File usr local lib python3 7 site packages dagster grpc client py line 154 in query docker example dagit | return self get response method request=request type kwargs timeout=timeout docker example dagit | File usr local lib python3 7 site packages dagster grpc client py line 129 in get response docker example dagit | return getattr stub method request metadata=self metadata timeout=timeout docker example dagit | File usr local lib python3 7 site packages grpc channel py line 946 in call docker example dagit | return end unary response blocking state call False None docker example dagit | File usr local lib python3 7 site packages grpc channel py line 849 in end unary response blocking docker example dagit | raise InactiveRpcError state docker example dagit | docker example dagit | location name=location name error string=<http error to|error to> string

Joris Ganne · Answer

`FROM python 3 7 slim` ENV ACCEPT EULA=Y RUN apt get update y amp amp apt get update amp amp apt get install y no install recommends curl gcc g++ gnupg unixodbc dev unixodbc Add SQL Server ODBC Driver 17 for Ubuntu 18 04 RUN curl | apt key add amp amp curl gt etc apt sources list d mssql release list amp amp apt get update amp amp apt get install y no install recommends allow unauthenticated msodbcsql17 mssql tools amp amp echo export PATH= $PATH opt mssql tools bin gt gt ~ bash profile amp amp echo export PATH= $PATH opt mssql tools bin gt gt ~ bashrc COPY requirements txt requirements txt RUN pip3 install r requirements txt Set $DAGSTER HOME and copy dagster instance there ENV DAGSTER HOME= opt dagster dagster home RUN mkdir p $DAGSTER HOME COPY dagster yaml $DAGSTER HOME Add repository code WORKDIR opt dagster app COPY repo py opt dagster app Run dagster gRPC server on port 4000 EXPOSE 4000 CMD allows this to be overridden from run launchers or executors that want to run other commands against your repository CMD dagster api grpc h 0 0 0 0 p 4000 f repo py

Daniel Galea · Answer

Hey Are you running Dagit the Dagster daemon and the user code on the same Docker network

Daniel Galea · Answer

I am using this docker compose file to run Dagster locally including a postgres database `version 3 7 ` `services ` ` This service runs the postgres DB used by dagster for run storage schedule storage ` ` and event log storage ` `docker example postgresql ` `image postgres 11` `container name docker example postgresql` `environment ` `POSTGRES USER postgres user ` `POSTGRES PASSWORD postgres password ` `POSTGRES DB postgres db ` `networks ` ` docker example network` ` This service runs the gRPC server that loads your user code in both dagit` ` and dagster daemon By setting DAGSTER CURRENT IMAGE to its own image we tell the` ` run launcher to use this same image when launching runs in a new container as well ` ` Multiple containers like this can be deployed separately each just needs to run on` ` its own port and have its own entry in the workspace yaml file that s loaded by dagit ` `docker example user code ` `build ` `context ` `dockerfile Dockerfile user code dev` `container name docker example user code` `image docker example user code image` `restart always` `environment ` `DAGSTER POSTGRES USER postgres user ` `DAGSTER POSTGRES PASSWORD postgres password ` `DAGSTER POSTGRES DB postgres db ` `DAGSTER CURRENT IMAGE docker example user code image ` `networks ` ` docker example network` ` This service runs dagit which loads your user code from the user code container ` ` Since our instance uses the QueuedRunCoordinator any runs submitted from dagit will be put on` ` a queue and later dequeued and launched by dagster daemon ` `docker example dagit ` `build ` `context ` `dockerfile Dockerfile dagster dev` `entrypoint ` ` dagit` ` h` ` 0 0 0 0 ` ` p` ` 3000 ` ` w` ` workspace yaml` `container name docker example dagit` `expose ` ` 3000 ` `ports ` ` 3000 3000 ` `environment ` `DAGSTER POSTGRES USER postgres user ` `DAGSTER POSTGRES PASSWORD postgres password ` `DAGSTER POSTGRES DB postgres db ` `volumes Make docker client accessible so we can terminate containers from dagit` ` var run docker sock var run docker sock` ` tmp io manager storage tmp io manager storage` `networks ` ` docker example network` `depends on ` ` docker example postgresql` ` docker example user code` ` This service runs the dagster daemon process which is responsible for taking runs` ` off of the queue and launching them as well as creating runs from schedules or sensors ` `docker example daemon ` `build ` `context ` `dockerfile Dockerfile dagster dev` `entrypoint ` ` dagster daemon` ` run` `container name docker example daemon` `restart on failure` `environment ` `DAGSTER POSTGRES USER postgres user ` `DAGSTER POSTGRES PASSWORD postgres password ` `DAGSTER POSTGRES DB postgres db ` `volumes Make docker client accessible so we can launch containers using host docker` ` var run docker sock var run docker sock` ` tmp io manager storage tmp io manager storage` `networks ` ` docker example network` `depends on ` ` docker example postgresql` ` docker example user code` `networks ` `docker example network ` `driver bridge` `name docker example network`

Joris Ganne · Answer

Hey Daniel thank you for your reply I have put the two docker compose files yours and mine besides each other and they are exactly the same I haven t touched this file and without any changes so right from the example project I could perfectly run the example So I supposed that when I changed repo py and Dockerfile user code it would work

Daniel Galea · Answer

Hmm that s strange your Dockerfile is also similar to mine I don t copy in the dagster yaml file in the user code image but that shouldn t break anything What about the user deployment container what does `docker ps` return Is it running

Joris Ganne · Answer

Yes the docker user container is running slightly smiling face

Daniel Galea · Answer

I see I assume you also checked the container s logs slightly smiling face

Joris Ganne · Answer

At the moment I receive another error after trying different things Could not load location repo py to check for sensors due to the following error FileNotFoundError Errno 2 No such file or directory opt dagster dagster home repo py

Joris Ganne · Answer

This is the original error usr local lib python3 7 site packages dagster core workspace context py 586 UserWarning Error loading repository location repo py FileNotFoundError Errno 2 No such file or directory opt dagster dagster home repo py

Joris Ganne · Answer

The last error was my fault A space missing in workspace yaml Apologies for the inconvenience

Daniel Galea · Answer

No worries At least you got it fixed now slightly smiling face

Joris Ganne · Answer

The last error yes smile but unfortunately still struggling with grpc server error

Daniel Galea · Answer

Ahh well from what I can see you are copying your repo py file into opt dagster app but it is trying to get loaded from opt dagster dagster home

Daniel Galea · Answer

I am referring to this part of your Dockerfile `WORKDIR opt dagster app` `COPY repo py opt dagster app` ` Run dagster gRPC server on port 4000` `EXPOSE 4000` ` CMD allows this to be overridden from run launchers or executors that want` ` to run other commands against your repository` `CMD dagster api grpc h 0 0 0 0 p 4000 f repo py `

Daniel Galea · Answer

I think it s because you are manually setting $DAGSTER HOME as I said I don t do this in my Dockerfile for the user deployment code Mine looks like this `FROM python 3 7 slim` ` Checkout and install dagster libraries needed to run the gRPC server` ` exposing your repository to dagit and dagster daemon and to load the DagsterInstance` `COPY requirements user code txt requirements user code txt` `RUN pip install r requirements user code txt` `WORKDIR opt dagster app` `ENV PLATFORM ENVIRONMENT=DEV` `COPY dagster src opt dagster app dagster src` ` Run dagster gRPC server on port 4000` `EXPOSE 4000` ` CMD allows this to be overridden from run launchers or executors that want` ` to run other commands against your repository` `CMD dagster api grpc h 0 0 0 0 p 4000 f dagster src repo py `