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

dagster

Hi, has anyone from the dev team this
<https://github.com/dagster-io/dagster/issues/8481>
still in mind? I still believe this is an absolute nogo to NOT use the intended command and instead put everything into args. This is a hack which must be reverted. Also, since 0.15.5 not even the tini workaround works!

Please, fix this. Deploying dagster runs onto Azure ACI is impossible with this! ACI insists on being provided a command in the container spec!

The tini workaround is still broken in 0.15.7!

Hi Timo - we can take a look at what changed in 0.15.5 - but no immediate plans to revert that PR, no

let me see if I can reproduce locally the command not being passed in if it's set in container_config

<https://github.com/dagster-io/dagster/pull/8161> jumps out as a likely cause of command behaving differently as of 0.15.5, investigating further

<https://github.com/dagster-io/dagster/pull/9037> should make your workaround for ACI work again and we should be able to get that out on Thursday - thanks for the report and apologies for the delay in the response

Appreciate the feedback about it feeling like a hack - ultimately reverting it would be a breaking change for a bunch of folks, so we just need to balance that as a consideration too. Main priority right now is unblocking you and fixing the regression in your workaround

<@U016C4E5CP8> Thanks so far. Really appreciated.  As far as I remember, originally the decision to have the whole command in args was that someone wanted to set the conda env with the docker entrypoint. I mean there are other ways to achieve that.