-
Notifications
You must be signed in to change notification settings - Fork 4.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to upgrade a connector from a private registry #32953
Comments
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: |
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 |
Seems that fetching registry entry fails even when pulling not from a private registry: #34198 |
At Airbyte, we seek to be clear about the project priorities and roadmap. This issue has not had any activity for 180 days, suggesting that it's not as critical as others. It's possible it has already been fixed. It is being marked as stale and will be closed in 20 days if there is no activity. To keep it open, please comment to let us know why it is important to you and if it is still reproducible on recent versions of Airbyte. |
This issue was closed because it has been inactive for 20 days since being marked as stale. |
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
The text was updated successfully, but these errors were encountered: