Open philippeboyd opened 9 months ago
I had the same issue when I was trying to build the docker image using an apple silicon (and airbyte was running in an amd64). I fixed it by building the docker image using buildx: docker buildx build --platform linux/amd64 -t my_tag .
Hi @mcornejo I'm building on macOS Intel (x86_64) and Airbyte is also deployed on a x86_64
The error is due to the fact that Airbyte still http requests the image from the private registry Failed to fetch registry entry ...
Seems that fetching registry entry fails even when pulling not from a private registry: https://github.com/airbytehq/airbyte/issues/34198 I confirm to hit the same bug on 0.50.43 with private registry
What method are you using to run Airbyte?
Docker
Platform Version or Helm Chart Version
0.50.34
What step the error happened?
Other
Revelant information
We used to be able to upgrade connectors from private registry as long as they are pulled on the machine prior. Now we're unable to upgrade a connector from private registry we get the error
When executing
docker images
my image is present on the machine.Something either changed in
io.airbyte.config.persistence.ActorDefinitionVersionResolver
and/orio.airbyte.config.specs.RemoteDefinitionsProvider
Relevant log output