Levan
10/19/2021, 10:19 AMworkplace.yml
for deploy_docker example?
When I try adding
load_from:
# - grpc_server:
# host: docker_example_pipelines
# port: 4000
# location_name: "example_pipelines"
- python_file:
relative_path: repo.py
executable_path: /opt/conda/envs/test/bin/python
Run queue gives error Caught an error for run c59de7e6-0b8e-48e4-a45a-86e33ccc0881 while removing it from the queue. Marking the run as failed and dropping it from the queue: Exception: No docker image specified by the instance config or repository
daniel
10/19/2021, 12:52 PMpython_file
when using that example - instead, you would most likely change the Dockerfile you use to build the pipeline imageLevan
10/19/2021, 1:20 PMdaniel
10/19/2021, 1:44 PMLevan
10/19/2021, 1:54 PMdaniel
10/26/2021, 2:12 PMLevan
10/27/2021, 12:54 PMdaniel
10/27/2021, 1:20 PMLevan
01/21/2022, 3:56 PMdaniel
01/21/2022, 4:05 PM--use-python-environment-entry-point
flag now for the dagster api grpc
command that I think will make it work the way that you want (when runs are launched, they will use the same python environment in which the gRPC server was launched: https://docs.dagster.io/_apidocs/cli#cmdoption-dagster-api-grpc-use-python-environment-entry-point)dagster
entry point)Levan
01/21/2022, 7:26 PMArnoud van Dommelen
09/20/2022, 8:02 AM--use-python-environment-entry-point
is removed since Dagster version 1.0.0. Is it now the case that it gets the python environment of the corresponding gRPC by default? Or has there become a different solution for having multiple python environments?
Thank you in advance!daniel
09/20/2022, 11:27 AMArnoud van Dommelen
09/20/2022, 11:53 AMdaniel
09/20/2022, 12:11 PM