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

dagster

Is there some tag I can specify to keep the container running (for debugging purposes) and not kill it right away? There was once an undocumented flag to execute the job within the default container (but I forgot the name)

Are you using the `DockerRunLauncher`? If so, I think you can forward the `auto_remove`<https://docker-py.readthedocs.io/en/stable/containers.html#docker.models.containers.ContainerCollection.run| Docker flag> to the container using the `container_kwargs` <https://docs.dagster.io/_apidocs/libraries/dagster-docker#dagster_docker.DockerRunLauncher|config field in the run launcher>

```run_launcher:
  module: dagster_docker
  class: DockerRunLauncher
  config:
    container_kwargs:
      auto_remove: false```

yes but Is it also possible to do this directly from the UI?

Is this special tag still applicable (no run isolation also for hybrid deployments)? if yes, what was the name of it?

Or is there a special tag I can set to feed this config to the run launcher from a tag/dagit UI?

Hmm, I think the run launcher config is not customizable by tags currently

and for this experimental tag to re-use the single base container is this one still working? And if yes, what is the name?

<@U016C4E5CP8> <https://github.com/dagster-io/dagster/discussions/14771>

Hey Georg, I’m not sure what the experimental tag or single base container that you’re referring to here is. Can you elaborate or point to a doc or previous post where it was discussed?

I think it is `dagster/isolation:disabled` .

And it was experimental for hybrid deployments

The single base container is the default deployment of the code location which is spun up by dagster

Ah, non isolated runs, got it. I’m not aware of any recent changes from the previous behavior