Getting this error via docker-compose with 0.14.5 ...
# ask-community
g
Getting this error via docker-compose with 0.14.5 (though not necessarily specific to it). I'm not using any volume mounting in the docker-compose.yml. Apart from for docker.sock
Copy code
docker_dev_dagster_daemon        | 2022-05-18 16:14:41 +0000 - dagster.daemon.QueuedRunCoordinatorDaemon - INFO - Retrieved 1 queued runs, checking limits.
docker_dev_dagster_daemon        | 2022-05-18 16:14:42 +0000 - dagster.daemon.QueuedRunCoordinatorDaemon - ERROR - Caught an error for run 76993f4b-79a0-407c-89ef-7b0292cedba1 while removing it from the queue. Marking the run as failed and dropping it from the queue: docker.errors.APIError: 400 Client Error for <http+docker://localhost/v1.41/containers/dec25becd6ff10f648e77184d2aee45e4de742cf41eeeb561120e5682e924d89/start>: Bad Request ("failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error mounting "/opt/dagster/repo.py" to rootfs at "/opt/dagster/app/repo.py": mount /opt/dagster/repo.py:/opt/dagster/app/repo.py (via /proc/self/fd/6), flags: 0x5000: not a directory: unknown: Are you trying to mount a directory onto a file (or vice-versa)? Check if the specified host path exists and is the expected type")
docker_dev_dagster_daemon        | 
docker_dev_dagster_daemon        | Stack Trace:
docker_dev_dagster_daemon        |   File "/usr/local/lib/python3.9/site-packages/dagster/daemon/run_coordinator/queued_run_coordinator_daemon.py", line 155, in run_iteration
docker_dev_dagster_daemon        |     self._dequeue_run(instance, run, workspace)
docker_dev_dagster_daemon        |   File "/usr/local/lib/python3.9/site-packages/dagster/daemon/run_coordinator/queued_run_coordinator_daemon.py", line 230, in _dequeue_run
docker_dev_dagster_daemon        |     instance.launch_run(run.run_id, workspace)
docker_dev_dagster_daemon        |   File "/usr/local/lib/python3.9/site-packages/dagster/core/instance/__init__.py", line 1732, in launch_run
docker_dev_dagster_daemon        |     self._run_launcher.launch_run(LaunchRunContext(pipeline_run=run, workspace=workspace))
docker_dev_dagster_daemon        |   File "/usr/local/lib/python3.9/site-packages/dagster_docker/docker_run_launcher.py", line 152, in launch_run
docker_dev_dagster_daemon        |     self._launch_container_with_command(run, docker_image, command)
docker_dev_dagster_daemon        |   File "/usr/local/lib/python3.9/site-packages/dagster_docker/docker_run_launcher.py", line 139, in _launch_container_with_command
docker_dev_dagster_daemon        |     container.start()
docker_dev_dagster_daemon        |   File "/usr/local/lib/python3.9/site-packages/docker/models/containers.py", line 404, in start
docker_dev_dagster_daemon        |     return self.client.api.start(self.id, **kwargs)
docker_dev_dagster_daemon        |   File "/usr/local/lib/python3.9/site-packages/docker/utils/decorators.py", line 19, in wrapped
docker_dev_dagster_daemon        |     return f(self, resource_id, *args, **kwargs)
docker_dev_dagster_daemon        |   File "/usr/local/lib/python3.9/site-packages/docker/api/container.py", line 1109, in start
docker_dev_dagster_daemon        |     self._raise_for_status(res)
docker_dev_dagster_daemon        |   File "/usr/local/lib/python3.9/site-packages/docker/api/client.py", line 270, in _raise_for_status
docker_dev_dagster_daemon        |     raise create_api_error_from_http_exception(e)
docker_dev_dagster_daemon        |   File "/usr/local/lib/python3.9/site-packages/docker/errors.py", line 31, in create_api_error_from_http_exception
docker_dev_dagster_daemon        |     raise cls(e, response=response, explanation=explanation)
docker_dev_dagster_daemon        |
🤖 1
I'm still very confused by this
Think I've realised I'd left volume mounting in the dagster.yaml that shouldn't have been there.
d
Hey George - the error message would definitely point to some kind of mounting of /opt/dagster/app/repo.py still happening somewhere, yeah - dagster doesn't do anything like that automatically
g
Yeah removing some volume mounting resolved it. Baffled by a new good'n:
Copy code
dagster_dbt.errors.DagsterDbtCliFatalRuntimeError: Fatal error in the dbt CLI (return code 2)
  File "/usr/local/lib/python3.9/site-packages/dagster/grpc/impl.py", line 81, in core_execute_run
    recon_pipeline.get_definition()
  File "/usr/local/lib/python3.9/site-packages/dagster/core/definitions/reconstruct.py", line 173, in get_definition
    defn = self.repository.get_definition().get_pipeline(self.pipeline_name)
  File "/usr/local/lib/python3.9/site-packages/dagster/core/definitions/reconstruct.py", line 82, in get_definition
    return repository_def_from_pointer(self.pointer)
  File "/usr/local/lib/python3.9/site-packages/dagster/core/definitions/reconstruct.py", line 649, in repository_def_from_pointer
    target = def_from_pointer(pointer)
  File "/usr/local/lib/python3.9/site-packages/dagster/core/definitions/reconstruct.py", line 570, in def_from_pointer
    target = pointer.load_target()
  File "/usr/local/lib/python3.9/site-packages/dagster/core/code_pointer.py", line 176, in load_target
    module = load_python_file(self.python_file, self.working_directory)
  File "/usr/local/lib/python3.9/site-packages/dagster/core/code_pointer.py", line 86, in load_python_file
    return import_module_from_path(module_name, python_file)
  File "/usr/local/lib/python3.9/site-packages/dagster/seven/__init__.py", line 50, in import_module_from_path
    spec.loader.exec_module(module)
  File "<frozen importlib._bootstrap_external>", line 850, in exec_module
  File "<frozen importlib._bootstrap>", line 228, in _call_with_frames_removed
  File "repo.py", line 21, in <module>
    from pipelines.analytics.dbt_analytics_assets import dbt_analytics_assets
  File "/opt/dagster/app/pipelines/analytics/dbt_analytics_assets.py", line 15, in <module>
    dbt_assets = load_assets_from_dbt_project(
  File "/usr/local/lib/python3.9/site-packages/dagster_dbt/asset_defs.py", line 237, in load_assets_from_dbt_project
    manifest_json, cli_output = _load_manifest_for_project(
  File "/usr/local/lib/python3.9/site-packages/dagster_dbt/asset_defs.py", line 32, in _load_manifest_for_project
    cli_output = execute_cli(
  File "/usr/local/lib/python3.9/site-packages/dagster_dbt/cli/utils.py", line 97, in execute_cli
    raise DagsterDbtCliFatalRuntimeError(logs=logs, raw_output=raw_output)
I can't have paths completely wrong because the assets are showing up perfectly in the UI, it's only when I go to execute them.
Works perfectly directly with dagit
Must be env variable or package difference
d
possible to make a new post for this? I'm not a dbt expert but can surface it to the people who are
1
g
Sorry, in bad habits with that.
d
no prob!