Hey all, just looking for some further clarification on the proper usage of storage = Docker() and KubernetesRun() together. Could someone shine some light on why I can deploy and run a flow with the storage=Docker(...dockerfile="my dockerfile") [with confirmed EC2 activity and successful front end runs], but when I mute that dockerfile param and instead try to use KubenernetesRun(image="my image here") with the same kind of registry as the Docker storage destination, my private packages are missing? In my case, both images are built from the same Dockerfile, the latter scenario just involves pushing to a repo first and attempting to call it with KubernetesRun().

Hi Charles! Are you using Docker storage in both cases? If so, your Docker storage image will always take precedent; if you want to use other images via the Run Config you’ll need to switch to a different storage model (e.g., S3)

AH that would totally explain it thanks! Yeah, suppose I incorrectly assumed if I didn't declare an actual image in Docker() it would look for an image in KubernetesRun(), that's my bad!

No worries, totally understandable!