https://linen.dev logo
Join Slack
Powered by
I am running into an error adding the source I cre...
# connector-development
w
I am running into an error adding the source I created to Airbyte running locally via 
docker-compose up
. All of the python and docker commands in this guide succeed, but when I try to add the source from the UI at 
localhost:8000
, it errors out. It seems like it's unable to pull the spec based on the error message: 
airbyte-worker      | Caused by: io.temporal.failure.ApplicationFailure: message='Error while getting spec from image airbyte/source-kyriba:dev', type='io.airbyte.workers.WorkerException', nonRetryable=false
Any ideas how to get this source running locally?
m
The Airbyte Server is running locally or are you doing a ssh-tunnel to your machine?
w
Airbyte server is running locally with 
docker-compose up
from the root directory (also tried with 
sudo
)
I wonder if it's because I'm on an m1 device. When I 
docker-compose up
initially (for the first time, or after 
docker-compose down --volumes --remove-orphans
) it ends up waiting on the 
airbyte-server
forever. If I kill it and then 
up
again the server is accessible.
just tried on my personal computer running fedora and ran into the same error. Seems like it's either a problem with my source, or somewhere in docker. The former is more likely, but not sure how to identify it given all the docker commands are working for my source.
I put up a PR with my code, so the diff is easy to identify if that's helpful https://github.com/wjwatkinson/airbyte/pull/1
running: from 
airbyte/airbyte-integrations/connectors/source-kyriba
docker  build . -t airbyte/source-kyriba:dev
from 
airbyte/
docker-compose up
m
yes for mac m1 you need to debug more, a few connectors doesn’t work with this architecture and Airbyte itself need some changes and build from scratch with those changes
w
ran into the same issue on a thinkpad running fedora, so thinking there might be another issue
to close out this thread everything worked on google cloud, so must have been an m1 problem. Not sure why fedora didn't work, but that's okay
3 Views
Open in Slack
PreviousNext
Powered by