-
Apache Airflow version2.10.4 If "Other Airflow 2 version" selected, which one?No response What happened?The documentation at https://airflow.apache.org/docs/docker-stack/build.html#build-build-image suggests that it should be possible to run What you think should happen instead?
How to reproduce
That's really it: you'll see the "invalid signature" errors and a return code of 100. Operating SystemPRETTY_NAME="Debian GNU/Linux 12 (bookworm)" NAME="Debian GNU/Linux" VERSION_ID="12" VERSION="12 (bookworm)" VERSION_CODENAME=bookworm ID=debian HOME_URL="https://www.debian.org/" SUPPORT_URL="https://www.debian.org/support" BUG_REPORT_URL="https://bugs.debian.org/" Versions of Apache Airflow Providersn/a DeploymentOther Docker-based deployment Deployment detailsn/a -- this is an issue with the docker image itself Anything else?No response Are you willing to submit PR?
Code of Conduct
|
Beta Was this translation helpful? Give feedback.
Replies: 6 comments 1 reply
-
|
I highly doubt it. The image is continously being built and updated in airflow CI and it would be visible if it happens. Very likely what you have is you are behind a company proxy that is messing with certificates/sites. |
Beta Was this translation helpful? Give feedback.
-
|
Converted it to a discussion if needed. |
Beta Was this translation helpful? Give feedback.
-
|
Also - before replying, if you have any doubts - try it on a plain system without any proxy and you will see that it works. If it did not, we would likely have 100s of people posting here. |
Beta Was this translation helpful? Give feedback.
-
|
I understand that this seems unlikely, but there is 100% definitely no proxy involved here unless Verizon FIOS is transparently proxying my traffic. Also, the error isn't that it can't fetch the InRelease file from the apt repository, it's that it can't validate the GPG signature on the file. That said I agree that it seems like more people than me would be complaining if this were the case. I'm going to go try a few things and report back. :) |
Beta Was this translation helpful? Give feedback.
-
So maybe your DNS is compromised and someone tries to attack you. That would explain why GPG signatures are wrong. Another option is that system time on your machine are set wrongly and those invalid signatures are expired or something. Also it could be it was a temporary blip |
Beta Was this translation helpful? Give feedback.
-
|
Welp, I nuked my local docker image repository to bedrock ( I'm frankly a little baffled-- as far as I understand it shouldn't be possible to corrupt an image or layer, and the image-id was correct (5f9a655d4ba7). But that's certainly not your problem. 😂 |
Beta Was this translation helpful? Give feedback.
-
|
It could be you simply run out of space on docker machine (if you are on mac for example - there is a limiited default space for the VM). I saw VERY weird errors when you run out of disk space while building the image. It could be for example in this case that signatures were written down locally and the files were zeroad due to lack of disk space (which is what happens when you run out of space) - and then they will be obviously invalid. I recommend running |
Beta Was this translation helpful? Give feedback.
Welp, I nuked my local docker image repository to bedrock (
docker image ls| awk '{print $3}'|grep -v IMAGE | xargs docker image rm -f) and suddenly: