Hey @Marvin, I have a prefect.yaml that has a build step similar to the example below:

build:
- prefect_docker.deployments.steps.build_docker_image:
  requires: prefect-docker>=0.3.0
  image_name: my-repo/my-image
  tag: my-tag
  dockerfile: auto
  push: true

When I run

prefect deploy

I see the error

TypeError: BuildApiMixin.build() got an unexpected keyword argument 'push'

. I see that in prefect_docker the client used to build the Dockerfile in the build step is from docker-py. Under `build`s parameters I do not see a

push

option listed, only

pull

. Is the error above expected? Is the snippet above from the documentation correct?

It appears that the error you're encountering with the

push

keyword argument is unexpected based on the documentation for Prefect 3.x. The snippet you provided seems to be correct according to the documentation that describes the usage of

push: true

in the

prefect_docker.deployments.steps.build_docker_image

step source. Given that there were no related issues found on GitHub and your usage matches the documentation, your setup should typically work. It might be worth checking if there are any updates or bug fixes relevant to your Prefect version in the latest release notes here. Ensure that your Prefect and

prefect-docker

versions meet the required versions specified in the

prefect.yaml

. If everything is correct and the error persists, it could be beneficial to post the issue in the Prefect community or support forums for more targeted troubleshooting.

ah! so

push_docker_image

is a separate step now so where did you find that? we may need to update docs

Yes, we are using Prefect 3.0.10 and I found the examples here https://docs.prefect.io/3.0/deploy/infrastructure-concepts/prefect-yaml. I was thinking of suggesting an edit to the docs but wanted to verify first

sweet - thank you! we'll get that updated

I think there are also 2 other

push

examples here https://docs.prefect.io/3.0/deploy/infrastructure-concepts/prefect-yaml#reuse-configuration-across-deployments and https://docs.prefect.io/3.0/deploy/infrastructure-concepts/prefect-yaml#the-build-action

aha! thank you - ill update those as well

Following up from yesterday, @Nate if we have suggestions or fixes for the docs how best should we submit those requests? For example the link "overriding a work pool's job variables" results in a 404 and is not easy to find from the main prefect documentation. https://github.com/PrefectHQ/prefect/blob/main/docs/3.0/deploy/infrastructure-concepts/workers.mdx#additional-resources

https://github.com/PrefectHQ/prefect/issues/new/choose but in this case, this is because our docs hosting platform handles the base path for us, so the link isnt a valid url if viewed directly in the .mdx file (this is expected). if you click on the link here, you'll see its valid heres the actual page of the docs which you can get to by using Cmd+K to search or via the nav: Deploy > Run flows on dynamic infra > this page

Ah I see, thank you!