Hello again Yes I m back sweat smile The problem Pointing to

Question

Hello again Yes I m back sweat smile The problem Pointing to the private registry a `DockerRegistry` block through the `image registry` parameter of `DockerContainer` doesn t work I can tell that by looking at the Docker registry field in the GUI is still empty This means I have to manually go to the GUI and point it to the registry I don t want to set it myself each time how do I accomplish this through the library

Nate · Answer

hi < Ajeel Ahmed> can you share what you re trying programmatically that you re saying has no effect

Nate · Answer

hmm okay I ve reproduced this i think this is a UI problem when I load the saved block programmatically it still has the registry attached

Ajeel Ahmed · Answer

it does not update yes so when I try to run the flow when the docker registry field is empty it crashes so I have to go to GUI update the field myself and then run the flow and then it does work

Ajeel Ahmed · Answer

I hope you get what I m trying to say haha

Nate · Answer

gt when the docker registry field is empty it crashes so I have to go to GUI update the field myself this is surprising to me because i see that the registry stays attached to the `DockerContainer` below I would expect that when the agent pulls the `DockerContainer` that it still has the `image registry` filled out even if the UI doesn t show it for some reason ```In 5 DockerContainer image registry=registry Out 5 DockerContainer type= docker container env= labels= name=None command=None image= prefecthq prefect 2 10 8 python3 10 image pull policy=None image registry=DockerRegistry username= zzstoatzz password=SecretStr registry url= reauth=True networks= network mode=None auto remove=False volumes= stream output=True memswap limit=None mem limit=None privileged=False In 6 DockerContainer image registry=registry save test Out 6 UUID e49c230d 5017 4000 aae3 85346b55124f In 7 exit ipython In 1 from prefect infrastructure docker import DockerContainer DockerRegistry In 2 DockerContainer load test Out 2 DockerContainer type= docker container env= labels= name=None command=None image= prefecthq prefect 2 10 8 python3 10 image pull policy=None image registry=DockerRegistry username= zzstoatzz password=SecretStr registry url= reauth=True networks= network mode=None auto remove=False volumes= stream output=True memswap limit=None mem limit=None privileged=False ```

Ajeel Ahmed · Answer

``` registry block = DockerRegistry load gitlab docker registry infra block = DockerContainer image registry=registry block image= link to the image image pull policy= ALWAYS networks= network stuff env=asdict Config auto remove=True stream output=True ```

Ajeel Ahmed · Answer

this is the code

Ajeel Ahmed · Answer

here s the thing the documentation says the image parameter should take in the tag of the docker image does that mean I m supposed to only put the tag name Like `latest` If so where am I supposed to put the link to the image

Ajeel Ahmed · Answer

you can see it here

Nate · Answer

im pretty sure that docstring is slightly misleading and `image` wants something like `registry image tag` can you share the logs from when it crashes

Ajeel Ahmed · Answer

yeah sure just give me a sec

Ajeel Ahmed · Answer

```2023 05 18 22 46 03 21 46 03 494 | DEBUG | prefect agent Checking for cancelled flow runs 2023 05 18 22 46 13 21 46 13 368 | DEBUG | prefect agent Checking for cancelled flow runs 2023 05 18 22 46 16 21 46 16 759 | DEBUG | prefect agent Checking for scheduled flow runs 2023 05 18 22 46 27 21 46 27 000 | DEBUG | prefect agent Checking for scheduled flow runs 2023 05 18 22 46 27 21 46 27 184 | DEBUG | prefect agent Checking for cancelled flow runs 2023 05 18 22 46 35 21 46 35 382 | DEBUG | prefect agent Checking for scheduled flow runs 2023 05 18 22 46 35 21 46 35 864 | INFO | prefect agent Submitting flow run 4e3de005 6c51 492d 8bf7 437c6088167c 2023 05 18 22 46 36 21 46 36 954 | DEBUG | prefect infrastructure docker container Could not find Docker image locally 2023 05 18 22 46 36 21 46 36 958 | INFO | prefect infrastructure docker container Pulling image 2023 05 18 22 46 38 21 46 37 980 | ERROR | prefect agent Failed to submit flow run 4e3de005 6c51 492d 8bf7 437c6088167c to infrastructure 2023 05 18 22 46 38 Traceback most recent call last 2023 05 18 22 46 38 File usr local lib python3 10 site packages docker api client py line 268 in raise for status 2023 05 18 22 46 38 response raise for status 2023 05 18 22 46 38 File usr local lib python3 10 site packages requests models py line 1021 in raise for status 2023 05 18 22 46 38 raise HTTPError http error msg response=self 2023 05 18 22 46 38 requests exceptions HTTPError 500 Server Error Internal Server Error for url 2023 05 18 22 46 38 2023 05 18 22 46 38 The above exception was the direct cause of the following exception 2023 05 18 22 46 38 2023 05 18 22 46 38 Traceback most recent call last 2023 05 18 22 46 38 File usr local lib python3 10 site packages prefect agent py line 424 in submit run and capture errors 2023 05 18 22 46 38 result = await infrastructure run task status=task status 2023 05 18 22 46 38 File usr local lib python3 10 site packages prefect infrastructure docker py line 267 in run 2023 05 18 22 46 38 container = await run sync in worker thread self create and start container 2023 05 18 22 46 38 File usr local lib python3 10 site packages prefect utilities asyncutils py line 91 in run sync in worker thread 2023 05 18 22 46 38 return await anyio to thread run sync 2023 05 18 22 46 38 File usr local lib python3 10 site packages anyio to thread py line 31 in run sync 2023 05 18 22 46 38 return await get asynclib run sync in worker thread 2023 05 18 22 46 38 File usr local lib python3 10 site packages anyio backends asyncio py line 937 in run sync in worker thread 2023 05 18 22 46 38 return await future 2023 05 18 22 46 38 File usr local lib python3 10 site packages anyio backends asyncio py line 867 in run 2023 05 18 22 46 38 result = context run func args 2023 05 18 22 46 38 File usr local lib python3 10 site packages prefect infrastructure docker py line 365 in create and start container 2023 05 18 22 46 38 self pull image docker client 2023 05 18 22 46 38 File usr local lib python3 10 site packages prefect infrastructure docker py line 475 in pull image 2023 05 18 22 46 38 return docker client images pull image tag 2023 05 18 22 46 38 File usr local lib python3 10 site packages docker models images py line 465 in pull 2023 05 18 22 46 38 pull log = self client api pull 2023 05 18 22 46 38 File usr local lib python3 10 site packages docker api image py line 429 in pull 2023 05 18 22 46 38 self raise for status response 2023 05 18 22 46 38 File usr local lib python3 10 site packages docker api client py line 270 in raise for status 2023 05 18 22 46 38 raise create api error from http exception e from e 2023 05 18 22 46 38 File usr local lib python3 10 site packages docker errors py line 39 in create api error from http exception 2023 05 18 22 46 38 raise cls e response=response explanation=explanation from e 2023 05 18 22 46 38 docker errors APIError 500 Server Error for Internal Server Error Head denied access forbidden ```

Ajeel Ahmed · Answer

this is the error when the field for the Docker Registry is empty

Ajeel Ahmed · Answer

so when I fill it with the Docker Registry block it s supposed to have the one that is in the code above and run the flow again it runs just fine

Nate · Answer

hmm this seems like a bug then would you be willing to <https github com PrefectHQ prefect issues new choose|open an issue>

Ajeel Ahmed · Answer

oh yeah of course I was talking to a coworker and I was sure we were doing something wrong but good to know this is probably a bug

Nate · Answer

i could be missing something as well but its at least a little weird since the registry block should definitely appear in the UI after saving the block with the registry attached

Ajeel Ahmed · Answer

yeah we can close it if it s something on my side

Nate · Answer

+1

Ajeel Ahmed · Answer

Hey < Nate> hope you had a great weekend I thought I d investigate this issue a bit more before making an issue on GitHub and fortunately we realised the mistake our setup for blocks was failing and we weren t getting notified so it was not updating the blocks that were already there which made me think there was something wrong Fixed now Prefect works just fine Thanks again

Nate · Answer

thanks for digging into that and letting me know raised hands appreciate the update glad things are working