Kevin Schaich
02/21/2023, 5:53 AMdocker-compose.yml
example that parameterizes all config to a .env
file, and uses volumes to store code & data.
a. Container 1 = dagster-daemon
, uses above image
b. Container 2 = dagster-dagit
, uses above image
c. Container 3 = dagster-executor
, uses whatever image people want to run their code, such as a prebuilt python one from jupyter-stacks, and uses a bind mount to a local code directory rather than copying over a single repo.py
each time (not very helpful), as well as another bind mount to store results
d. Container 4 = db
– include an example which uses vanilla Postgres – although I suspect many people will have a preexisting one already they can use
The current docs are really confusing and ideally there'd be a simple block you could add to an existing docker-compose.yml
without a ton of fuss.claire
02/22/2023, 12:53 AMTim Castillo
02/22/2023, 8:39 PMKevin Schaich
02/23/2023, 12:28 AMKevin Schaich
02/23/2023, 12:41 AMKevin Schaich
02/23/2023, 12:41 AMKevin Schaich
02/27/2023, 8:52 PMTim Castillo
02/27/2023, 8:54 PMKevin Schaich
02/27/2023, 10:46 PMKevin Schaich
02/27/2023, 10:48 PMpython:3.7-slim
, because of the issues mentioned here https://github.com/dagster-io/dagster/issues/11353Kevin Schaich
02/27/2023, 10:50 PMDockerRunLauncher
, and the example here https://github.com/dagster-io/dagster/tree/1.1.20/examples/deploy_docker uses the old @repository
decorator which I think we should change to use the new Definitions
apiKevin Schaich
03/08/2023, 6:49 PMKevin Schaich
03/08/2023, 6:50 PMexamples/deploy_docker
folder?