https://linen.dev logo
Join Slack
Powered by
Hi - docker question - can anyone tell me what to ...
# replication-troubleshooting
s
Hi - docker question - can anyone tell me what to run to get airbyte local to pull in my nginx template changes in airbyte-proxy? I have tried 
docker-compose build
and 
docker-compose up --build
and neither seem to be doing anything. I can see in the code the chain of events that should produce the file /etc/nginx/nginx.conf: airbyte/airbyte-proxy/Dockerfile takes the template file and copies it to /etc/nginx/templates in the container Then the file airbyte/airbyte-proxy/run.sh uses that template to create etc/nginx/nginx.conf. At least that is how it looks from my limited understanding. But when i run docker-compose with --build option and copy out the nginx folder to check using 
docker cp airbyte-proxy:/etc/nginx .
, its the original unchanged file. How do i get it to take my changes? Should I just hit the delete button next to the 'proxy' image in the Docker Desktop UI and then run docker-compose up? Very new to docker and just don't want to break everything by accident!
✅ 1
update: deleted the airbyte/proxy image in docker desktop UI and ran 
docker-compose up
again. It's reappeared in images and still says created 23 days ago?? and has no changes to the nginx.conf. I'm pretty desperate at this point. Everything I do in the app gives me a non-json response error. Nobody has an answer and the only clue I've found is people saying you need to add something to the nginx config but never how to do it, and I have no idea how. I've been stuck for weeks on this 😞
for context - I'm trying to fix this error "client intended to send too large body: 1051296 bytes" which just shows up as 'non-json response' in the UI and is what I get when i try to set up even the smallest connection from salesforce to any destination (even selecting only 1 table to sync and to local csv). The fix i have seen is to add a line for client_max_body_size to nginx config, and that is where I am stumped.
m
@Stuart Horgan you must rebuild the 
airbyte-proxy
image
s
Hi @Marcos Marx (Airbyte) thanks for confirming I need to rebuild it. My question is how do i do this? I am trying the command 
docker-compose up --build
, which i have read is the command to use to rebuild the images, but it is not working for me. The 
--force-recreate
option is also not making a difference: my changes in airbyte/airbyte-proxy/nginx-auth.conf.template are not there when i check in the container at airbyte-proxy:/etc/nginx/templates/nginx-auth.conf.template. Any idea what I am missing?
@Marcos Marx (Airbyte) I deleted all containers and images in docker desktop ui then ran docker-compose to rebuild all of them, still my change is not there. It's like it's not even using my local directory to build the container
m
You must access the 
airbyte-proxy
and 
docker build . -t airbyte-proxy:{VERSION YOU DECIDED}
after change this in your docker-compose
If you run docker-compose up it will pull from dockerhub it won’t rebuild the containers.
s
Thanks so much for explaining @Marcos Marx (Airbyte) , this has worked for me! 🙌
j
@Marcos Marx (Airbyte) maybe a guide showing how to manage creating custom airbyte-proxy setups would be in order? There's a lot of questions around changing the nginx config.
2 Views
Open in Slack
PreviousNext
Powered by