The cloud-native orchestrator for the whole development lifecycle, with integrated lineage and observability.

dagster

Hi, we’re working on a dagster proof of concept running in AWS using the `EcsRunLauncher` . We have a service that defines the dagit and daemon containers, with our user code living in a different repository and communicating with dagit via grpc. We will have multiple repositories running grpc servers in the future and we’d like to have jobs launched from dagit use the task definition and image from their repo. I found <https://dagster.slack.com/archives/C014UDS8LAV/p1645489797390919|this thread> which describes our issue, but the last response was from 6 months ago. Is anyone aware of updates to this kind of configuration or know of a work around?

My problem has been solved. I needed
```  config:
    include_sidecars: true```
in my `EcsRunLauncher` config instead of
```config:
  task_definition: &lt;...&gt;
  container_name: &lt;....&gt;```
I thought the latter would let the image specified in `DAGSTER_CURRENT_IMAGE` from the grpc server be used as the image in the provided task definition for the `container_name` , but that is not the case. With the sidecars its working and no longer complaining about missing containers for use with firelens.