Hi! I got an error

dagster._core.errors.DagsterUserCodeUnreachableError: Could not reach user code server

when updating dagster locally to 1.1.1 from 0.14.9. Here's detail error :

grpc._channel._InactiveRpcError: <_InactiveRpcError of RPC that terminated with: status = StatusCode.UNAVAILABLE details = "DNS resolution failed for docker_dbt:4000: C-ares status is not ARES_SUCCESS qtype=A name=docker_dbt is_balancer=0: Domain name not found" debug_error_string = "{"created":"@1670495594.598923552","description":"DNS resolution failed for docker_dbt:4000: C-ares status is not ARES_SUCCESS qtype=A name=docker_dbt is_balancer=0: Domain name not found","file":"src/core/lib/transport/error_utils.cc","file_line":167,"grpc_status":14}" >
  File "/opt/conda/lib/python3.9/site-packages/dagster/_grpc/client.py", line 139, in _query
    return self._get_response(method, request=request_type(**kwargs), timeout=timeout)
  File "/opt/conda/lib/python3.9/site-packages/dagster/_grpc/client.py", line 129, in _get_response
    return getattr(stub, method)(request, metadata=self._metadata, timeout=timeout)
  File "/opt/conda/lib/python3.9/site-packages/grpc/_channel.py", line 946, in __call__
    return _end_unary_response_blocking(state, call, False, None)
  File "/opt/conda/lib/python3.9/site-packages/grpc/_channel.py", line 849, in _end_unary_response_blocking
    raise _InactiveRpcError(state)

Did I miss something when updating the version?

Hi Rama - this error indicates that your user code server isn’t running. Can you share more information about how/where you’re deploying dagster? (Docker/k8s/locally/etc)

Hi Daniel! I’m deploying locally.

Can you share more details about your code or project, is there a way that we can try to reproduce this problem ourselves?

I cannot share more details about the code cause it’s not my personal project. Do you think I miss something when update the version? What I did was just update the dockerfile

All I can tell you from that error message is that it’s having trouble finding the server where your code is running. I think we will need more information about your setup in order to be helpful here

what information do you need?

Ultimately what I need is a way to reproduce the problem myself - so if there’s a way to share a version of your Dockerfile or code with identifiable information removed, I could try running it and see if I hit the same problem

I used same python setup for dagster 0.14.9 version and worked fine. Do you think dagster 1.1.1 only compatible with certain python version?

1.1.1 should work on the same python versions as before. If there are any other logs you can share we could take a look

another error logs

debug_error_string = "{"created":"@1670849761.118030908","description":"DNS resolution failed for docker:4004: C-ares status is not ARES_SUCCESS qtype=A name=docker is_balancer=0: Domain name not found","file":"src/core/lib/transport/error_utils.cc","file_line":167,"grpc_status":14}"

I see docker in the error message there - are you deploying dagster on docker? details of that nature will be really helpful to understand what’s going on here and get this fixed

Here's my dockerfile

FROM continuumio/miniconda3:latest

RUN pip install dagster==1.1.1 dagit==1.1.1 dagster-graphql==1.1.1 dagster-postgres==0.17.1 dagster-aws==0.17.1

Nothing jumps out to me as a problem from that Dockerfile

yes, I can run the docker example. I don't see any different with mine

Got it - so just to make sure I understand the repro steps: • Run the docker example locally (by spinning up docker-compose) • Run that command in a separate terminal, it will error with a "grpc._channel._InactiveRpcError"?

Yes, you'll get error like this

Traceback (most recent call last):
  File "/Users/miniconda3/lib/python3.8/runpy.py", line 183, in _run_module_as_main
    mod_name, mod_spec, code = _get_module_details(mod_name, _Error)
  File "/Users/miniconda3/lib/python3.8/runpy.py", line 142, in _get_module_details
    return _get_module_details(pkg_main_name, error)
  File "/Users/miniconda3/lib/python3.8/runpy.py", line 153, in _get_module_details
    code = loader.get_code(mod_name)
AttributeError: 'AliasedModuleLoader' object has no attribute 'get_code'

I haven't seen that error before - it doesn't look like its part of a Dagster stack trace. I can ask around with the rest of the team to see if anybody has seen it before, but my suspicion is that the problem lies with your Python environment rather than a problem specific to Dagster. my first recommendation would be to try making a new conda environment and see if the problem persists there.

I read it in https://docs.dagster.io/concepts/code-locations/workspace-files, but maybe the docs already updated. Because I used version 0.14.9

"python -m dagster api grpc" Is actually probably best - I bet that will work

Thank you so much! really appreciate it!🙌