Hi team! I'm trying to build container for user deployments but running by a nonroot user. I'm curious about potential caveats. Especially I'd like to know about DAGSTER_HOME and if I should change it according to the nonroot user home?

Hi Mykola - I don't think user code deployments need to have DAGSTER_HOME set at all, so I don't expect any issues there. cc @johann who has investigated this in the past, but I don't recall any big Dagster-specific gotchas here.

@daniel, I have another related question. Current dagster-user-deployments approach uses

dagster

as an entry point (that is defined in helm chart). I'm curious about a possibility to use "distroless" images (https://github.com/GoogleContainerTools/distroless), which don't have "shell" and the stuff, but only python. So it would be great to make it possible to define my own entry point and params in Dockerfile.

dagster is going to inject the k8s args as "dagster api grpc" / "dagster api execute_run" / etc. and expect that to work - but you can point 'dagster' within your image at whatever executable you like, as long as those commands work