Hi - I am looking to use Docker storage, but I have a separate CI/CD workflow for pushing images to my docker registry — Is there any specific configurations I should be passing to denote that?--Or should I just omit the

registry_url

?

Hey @Leon Kozlowski , I guess you could that so it won’t push, but it doesnt seem ideal as it would still be built. Maybe you can use another storage but pass that container in your RunConfig (with DockerRun) so you don;t have to build?

Should have mentioned, I am looking to use KubernetsRun

I think what I mention would still apply where storage could be just your Flow and then Prefect would load that and run it on top of the provided Image. What you proposed with removing

registry_url

will work though

I am not sure I’m following

If for example you used Github Storage, it just stores the Flow. You can use GithubStorage + KubernetesRun with your container specified and Prefect will grab that flow from Github storage and run it on the container specified by KubernetesRun (not 100% sure but positive). I suggest this because DockerStorage will still build every time you register a flow, and it’s a painful experience for some users. Does that clarify?

I see

There is a sample repo here, but I think you have a different setup anyway. Checked with the team and Github Storage + KubernetesRun is preferred because DockerStorage is way more than people need most of the time