Bring your towel and join one of the fastest growing data communities. Welcome to our second-generation open source orchestration platform, a completely rethought approach to dataflow automation.

Prefect Community

<https://hub.docker.com/layers/prefecthq/prefect/2-python3.9/images/sha256-a2c961a967febbb5a7d79284df9eacc98939cc2625175687d0be53217ee5b169?context=explore|2.14.1-python3.9 docker image> just got pushed and I'm getting key errors on `apt update` hmmm
```#0 1.143 Err:1 <http://deb.debian.org/debian> bookworm InRelease
#0 1.143   At least one invalid signature was encountered.```
Is it me doing something dumb or the build is busted? Reverting to 2.14.0 "fixes" it.

hmm - thanks for the report <@U05JYU4PN94> 

we’ll look into this

my Dockerfile starts with:
```FROM prefecthq/prefect:2-python3.9
SHELL ["/bin/bash", "-c"]

RUN apt update
...```
and errors on that line
```------
Dockerfile:4
--------------------
   2 |     SHELL ["/bin/bash", "-c"]
   3 |     
   4 | >>> RUN apt update
ERROR: failed to solve: process "/bin/bash -c apt update" did not complete successfully: exit code: 100```

hm i dont think im quite able to reproduce this - trying a dockerfile with those lines is building for me okay

are you still running into this? someone else had a theory that there was an upstream issue with refreshing packages from debian (maybe?)

thank you so much for trying to replicate - confirming it is indeed something in the upstream. Running `docker system prune -a` resolved the issue :pray: