Michael Clawar
10/11/2021, 7:44 PMDAGSTER_CURRENT_IMAGE
variable set to "$REGISTRY_URL/<my-ecr-directory>/pipelines:$DAGSTER_IMAGE_TAG"
with an image tag tied to a commit hash, which loads correctly for the pipelines task/service, but is ignored for the dagster-run. Thanks!jordan
10/11/2021, 7:59 PMDAGSTER_CURRENT_IMAGE
in the pipelines service? In the example it defaults to latest https://github.com/dagster-io/dagster/blob/7ae9dffc389044690742a4bea19fbd6c820e7835/examples/deploy_ecs/docker-compose.yml#L103jordan
10/11/2021, 8:02 PMMichael Clawar
10/11/2021, 8:14 PMMichael Clawar
10/11/2021, 8:15 PM# This service runs a gRPC server that serves information about your
# repository. 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.
# Multiple containers like this can be deployed separately - each needs to
# run on its own port and have its own entry in the workspace.yaml file.
pipelines:
build:
context: .
dockerfile: ./Dockerfile
target: pipelines
image: "$REGISTRY_URL/<my-ecr-registry>/pipelines:$DAGSTER_IMAGE_TAG"
container_name: pipelines
command: "dagster api grpc -h 0.0.0.0 -p 4000 -f dagster_repository.py"
environment:
DAGSTER_PG_DB: "$DAGSTER_POSTGRES_DB"
DAGSTER_PG_HOST: "$DAGSTER_POSTGRES_HOSTNAME"
DAGSTER_PG_PASSWORD: "$DAGSTER_POSTGRES_PASSWORD"
DAGSTER_PG_USERNAME: "$DAGSTER_POSTGRES_USER"
DAGSTER_CURRENT_IMAGE: "$REGISTRY_URL/<my-ecr-repository>/pipelines:$DAGSTER_IMAGE_TAG"
Michael Clawar
10/11/2021, 8:15 PMMichael Clawar
10/11/2021, 8:20 PMDAGSTER_CURRENT_IMAGE
was set correctly to:
{
"name": "DAGSTER_CURRENT_IMAGE",
"value": "<REGISTRY_URL>/<my-ecr-repository>/pipelines:b4ea218de98329ab95d322190861d5fc2c82deeb"
}
so the tag made it there, but then the dagster-run task has no tag associated with it when I try to launch a run from the dagit UIMichael Clawar
10/11/2021, 8:30 PMjordan
10/11/2021, 8:30 PMMichael Clawar
10/11/2021, 8:53 PMjordan
10/11/2021, 8:59 PMMichael Clawar
10/11/2021, 9:00 PM