https://linen.dev logo
Join Slack
Powered by
however i am having some minor technical problems ...
# help-connector-development
k
however i am having some minor technical problems with deployment, i have published docker image with connector to my private mexus and i dont know how to configure airbyte to connect to nexus and use it
m
Please read the docs explaining how to use custom connectors with private registry: https://docs.airbyte.com/operator-guides/using-custom-connectors
đź‘Ť 1
k
Guys, but how can i configure airbyte worker to use my nexus?
just docker login inside the container??
m
yes, today airbyte doesn’t support the login to private registry in the UI. you must manually login to them
đź‘Ť 1
k
sure, where should i put 
daemon.json
file to be used by worker process??
“/etc/docker/“??
i have put it to /root/.docker i have also put the content (“insecure-registries”) to docker options
guys correct me if i am wrong - do i really need to rebuild entire docker air-byte worker image so i can “docker login” manually to my private repo by using daemon.json?
at the moment i have tried many methods to login and none of them works, there’s no default location where daemon.json is stored
m
did you try 
docker login
?
k
yes hundreds of times
i need to pass the options to “docker login” command
normally you do this by daemon.json file
normally its in home/.docker or /etc/docker/ location
but not inside airbyte worker
have been using plenty of methods none of them works
trying to pass insecure-registries
getting “INFO[0003] Error logging in to endpoint, trying next endpoint error=“Get”
my only idea is to rebuild airbyte worker docker image from the scratch
4 Views
Open in Slack
PreviousNext
Powered by