Deividas Jodogalvis
02/09/2024, 5:51 PMdagster job backfill
?Scout
02/09/2024, 5:51 PMdagster.yaml
(the instance configuration file) specifies the Docker image to use for launched jobs. The job_image
field should be set to the Docker image you want to use. For example:
yaml
run_launcher:
module: dagster_k8s.launcher
class: K8sRunLauncher
config:
job_image: "<http://mycompany.com/dagster-k8s-image:latest|mycompany.com/dagster-k8s-image:latest>"
# ... other configuration ...
2. Check the Repository Code: If the Docker image is not specified in the instance configuration, Dagster will attempt to use the image that was used to originally load the Dagster repository. Make sure that the repository code specifies the Docker image if it's not set in the instance configuration.
3. Check Environment Variables: If you are using environment variables to specify the Docker image, ensure that they are correctly set in the environment where the Dagster daemon or the command is running.
4. Check Permissions: If the Docker image is stored in a private registry, ensure that you have the correct permissions and that any required image_pull_secrets
are configured to allow Dagster to pull the image.
5. Validate the Docker Image: Make sure that the Docker image exists and is accessible from where you are running the dagster job backfill
command. You can test this by manually pulling the image using the Docker CLI.
If you've checked all the above and the issue persists, you may want to look at the specific job definition to ensure it's not overriding the Docker image configuration or missing it entirely.
Remember to apply these configurations in accordance with your deployment setup and the specifics of your Dagster instance and repository. If you need further assistance, please refer to the documentation or check for any relevant issues or discussions in the Dagster community that might provide additional context or solutions. Dagster-ecs unable to find dagster_postg... button Thank you for your feedback!