@Bianca Hoch has joined the channel

@Jeff Hale has joined the channel

@Ryan Peden has joined the channel

@Khuyen Tran has joined the channel

@Orbit has joined the channel

@Linen has joined the channel

@Discourse Integration has joined the channel

@Nelson Griffiths has joined the channel

@Oscar Björhn has joined the channel

@jawnsy has joined the channel

@Rob Freedy has joined the channel

@Nate has joined the channel

@John Mizerany has joined the channel

@Andrew Huang has joined the channel

@Esdras Lopes Nani has joined the channel

@Josh has joined the channel

@Anthony Head has joined the channel

Hi #prefect-docker - Does anybody have a reference to a Dockerfile with

prefecthq/prefect:2-latest

as base image, that they can run locally? I’m having hard time defining the

ENTRYPOINT

I am running into an error running a deployment on docker infrastructure. When triggering a deployment to run, it immediately turns up with a submission error (shared in comments). I have checked that docker is running on the machine and works. Not sure where else to look to debug? Anyone here in #prefect-docker seen this before?

For projects is it possible to enable buildkit for the build step using

prefect-docker

?

@alex I saw this PR and was wondering if you had an ETA? I need some of these features to be able to build in our CI/CD pipeline and am wondering if I should wait on this or create a workaround... https://github.com/PrefectHQ/prefect-docker/pull/51

Hi team! I've been enjoying using dockerized prefect jobs, but found that a flow run will constantly stuck in 'pending' state (and no logs show up in the Prefect Cloud UI!) if the docker command was fed through the command parameter in a cloud run block. It works fine if you run the flow with a CMD line in the dockerfile however. Is this doable and I'm missing something? Else this would be awesome as a feature request.

Hi everyone, Nice to meet you all, currently trying to run prefect on docker within my company network( that absolutely have a middleware proxy) and I want disabled the telemetry when starting the prefect server start I already added the config to disabled the telemetry in the /root/.prefect/config.toml but it seems to be ignored and still throwing failed to send telemetry below is the config I added, Thanks

Can someone help with a simple example of the new 'prefect deploy' on docker -- the docs don't have an example and its very difficult to pull together which configurations are needed among work-pool config (which can include image:tag), the prefect.yaml file

prefect_docker.projects.steps.build_docker_image

, etc. I am able to successfully deploy the toy

log_flow.py

flow on local process, no problem. Docker desktop is installed, the image is available locally as well as from dockerhub

prefecthq/prefect: 2.10.13-python3.11

. The deployment doesn't need to build the image, just run the container.

Hi all. I'm trying to migrate my Docker-based Prefect flows from Prefect Agent over to the new Prefect Worker. I have a couple of questions: 1. The Docker work pool doesn’t appear to have any settings relating to the container registry. How can I set it to use the Docker registry block that I have defined in Prefect? 2. Am I correct in thinking that I will need a separate Docker work pool for each image that I want to use in my jobs? For example if deployment

A

uses

my-org/image1:latest

and deployment

B

uses

my-org/image2:latest

, then these cannot share a work pool, instead I will need to create separate pools with different images configured on each one?

does the prefect-docker.DockerRegistryCredentials object allow you to login to a gcr registry?

Hello! I currently have a deployment using docker as an infrastructure block. But once that agent receives a job to run, it fails to submit this job for that infrastructure. Could you guys give a hand to resolve that?

raise cls(e, response=response, explanation=explanation) from e
docker.errors.APIError: 400 Client Error for <http+docker://localhost/v1.43/containers/create?name=zealous-marten>: Bad Request ("cannot share the host's network namespace when user namespaces are enabled"
16:29:57.583 | INFO    | prefect.agent - Completed submission of flow run '9b0d24b2-0584-4229-9d9d-3f8b754b9e28'
16:29:57.622 | INFO    | prefect.agent - Reported flow run '9b0d24b2-0584-4229-9d9d-3f8b754b9e28' as crashed: Flow run could not be submitted to infrastructure

The docs mention building your own images from scratch. Is there a description of what is required in the container or an example dockerfile to follow? https://docs.prefect.io/latest/concepts/infrastructure/?h=build#building-your-own-image

Hi, a Prefect agent we've been running for >2 months with no changes to suddenly stopped, with the following error. I exported the environment variables (where we are holding the prefect api_key and url values) and they are the correct values. Any idea why this suddenly is failing? The dockerfile used to deploy the prefect agent is using "FROM prefecthq/prefect:2-python3.10" The environment variables haven't changed as well. Locally running the prefect agent works fine

Hi! I’m trying to deploy a flow to run on a self-hosted Prefect server following this guide https://docs.prefect.io/latest/guides/docker/. I’ve been able to successfully build and run the image but I’m having trouble figuring out how to deploy the image to our remote server successfully and also how to trigger the flow from the remote server without it being dependent on my local machine. Any advice/documentation you could point me to?