Fernando Silveira
11/22/2022, 3:39 AMDockerContainer
storage block to my deployment indicating that it should just pull my docker image from AWS ECR and run the flow.
However, as far as I understand, the DockerContainer
block is also an infrastructure block and is meant to run the image against docker directly on a machine - i.e., NOT in a KubernetesJob
.
This means that so far, I've been relegated to using the S3
storage block which pushes my flow code to S3, only to pull it back to my docker image at flow run time (when the image already contains all the code it needs to run).
This feels wrong so I'm sure I must be missing something here. How do I configure KubernetesJob
to just pull a docker image and not rely on any additional storage block like S3?
PS: so far, I'm really enjoying how quickly I'm getting up to speed on prefect v2. Despite of kinks like this, I'm really enjoying the development experience.Zanie
11/22/2022, 4:08 AMimage
on your Kubernetes Job — although for ECR it’s a little tricky to authenticate.Fernando Silveira
11/22/2022, 4:10 AMZanie
11/22/2022, 4:10 AMFernando Silveira
11/22/2022, 4:11 AMZanie
11/22/2022, 4:12 AMFernando Silveira
11/22/2022, 4:12 AMZanie
11/22/2022, 4:13 AMFernando Silveira
11/22/2022, 4:13 AMZanie
11/22/2022, 4:13 AM--skip-upload
flag on the prefect deployment build
commandFernando Silveira
11/22/2022, 6:04 AM