Hello We have deployed Dagster using Helm chart for our user

Question

Hello We have deployed Dagster using Helm chart for our user code and we are able to see repository amp assets on dagit UI But when we run materialized the assets it fails with below error ```Error Got unexpected extra arguments dagster api execute run class ExecuteRunArgs instance ref class InstanceRef compute logs data class ConfigurableClassData class name NoOpComputeLogManager config yaml n module name dagster core storage noop compute log manager custom instance class data null event storage data class ConfigurableClassData class name PostgresEventLogStorage config yaml postgres db n db name dagster n hostname lt HOSTNAME REDACTED gt n params n password n env DAGSTER PG PASSWORD n port 5432 n username dagster rw n module name dagster postgres event log local artifact storage data class ConfigurableClassData class name LocalArtifactStorage config yaml base dir opt dagster dagster home n module name dagster core storage root run coordinator data class ConfigurableClassData class name DefaultRunCoordinator config yaml n module name dagster core run coordinator run launcher data class ConfigurableClassData class name K8sRunLauncher config yaml dagster home opt dagster dagster home nimage pull policy Always ninstance config map dagster instance njob namespace dagster nload incluster config true npostgres password secret dagster postgresql secret nservice account name dagster n module name dagster k8s run storage data class ConfigurableClassData class name PostgresRunStorage config yaml postgres db n db name dagster n hostname lt HOSTNAME REDACTED gt n params n password n env DAGSTER PG PASSWORD n port 5432 n username dagster rw n module name dagster postgres run storage schedule storage data class ConfigurableClassData class name PostgresScheduleStorage config yaml postgres db n db name dagster n hostname lt HOSTNAME REDACTED gt n params n password n env DAGSTER PG PASSWORD n port 5432 n username dagster rw n module name dagster postgres schedule storage scheduler data class ConfigurableClassData class name DagsterDaemonScheduler config yaml n module name dagster core scheduler secrets loader data null settings telemetry enabled true storage data class ConfigurableClassData class name CompositeStorage config yaml event log storage n class name PostgresEventLogStorage n config yaml postgres db n db name dagster n hostname lt HOSTNAME REDACTED gt n n params n password n env DAGSTER PG PASSWORD n port 5432 n username n dagster rw n n module name dagster postgres event log nrun storage n class name PostgresRunStorage n config yaml postgres db n db name dagster n hostname lt HOSTNAME REDACTED gt n n params n password n env DAGSTER PG PASSWORD n port 5432 n username n dagster rw n n module name dagster postgres run storage nschedule storage n class name PostgresScheduleStorage n config yaml postgres db n db name dagster n hostname lt HOSTNAME REDACTED gt n n params n password n env DAGSTER PG PASSWORD n port 5432 n username n dagster rw n n module name dagster postgres schedule storage n module name dagster core storage legacy storage pipeline origin class PipelinePythonOrigin pipeline name ASSET JOB 0 repository origin class RepositoryPythonOrigin code pointer class FileCodePointer fn name dbt schedules python file opt dagster app dagster trident bundling repository py working directory opt dagster app container context k8s env config maps dagster user deployments k8s dagster user code 1 user env env secrets dagster redshift creds image pull policy Always image pull secrets name boku docker creds namespace dagster service account name dagster user deployments user deployments container image <http artifactory boku com eng plt cd dagster 0 0 9|artifactory boku com eng plt cd dagster 0 0 9> entry point dagster executable path usr local bin python pipeline run id 0800f6ef 8b89 47d1 bcf7 82aba3a6abce set exit code on failure null ``` Can someone suggest how to troubleshoot the error

Abhishek Sawant · Answer

Below is the Value yaml ``` apiVersion <http helm toolkit fluxcd io v2beta1|helm toolkit fluxcd io v2beta1> kind HelmRelease metadata name dagster user deployments namespace dagster spec interval 1m chart spec chart dagster user deployments version 1 1 13 sourceRef kind HelmRepository name dagster helm namespace flux system interval 1m values postgresql enabled false postgresqlHost lt HOST REDACTED gt postgresqlUsername dagster rw postgresqlDatabase dagster generatePostgresqlPasswordSecret false dagsterHome opt dagster dagster home postgresqlSecretName dagster postgresql secret deployments name k8s dagster user code 1 image repository lt REPO REDACTED gt tag 0 0 9 pullPolicy Always dagsterApiGrpcArgs python file opt dagster app dagster trident bundling repository py port 3000 includeConfigInLaunchedRuns enabled true env REDSHIFT HOST lt HOST REDACTED gt REDSHIFT PORT 5439 REDSHIFT DB lt REDACTED gt envConfigMaps envSecrets name dagster redshift creds labels volumes volumeMounts annotations nodeSelector affinity tolerations podSecurityContext securityContext resources readinessProbe periodSeconds 20 timeoutSeconds 3 successThreshold 1 failureThreshold 3 livenessProbe startupProbe enabled false service annotations imagePullSecrets name lt REDACTED gt ```

daniel · Answer

Hi abhishek does the image that you re using have an entrypoint set Dagster injects a command bit doesn t set an entrypoint so if your ENTRYPOINT doesn t work when dagster is appended to it that might explain what you re seeing

Abhishek Sawant · Answer

It has ENTRYPOINT as `ENTRYPOINT dagit h 0 0 0 0 p 3000 `

daniel · Answer

I think if you replace that ENTRYPOINT with CMD instead the problem will go away

Abhishek Sawant · Answer

okay Let me try Thanks