Summary
The user is facing a 404 response from Airbyte when changing the API endpoint in Airbyte and Airflow Docker containers. They suspect the issue might be related to communication between Docker containers. They also suggest ensuring both containers are in the same network.
Question
Hi <@U05JENRCF7C>, I have the same issue. Did you manage to solve it?
I also have Airbyte and Airflow running with the latest version in Docker containers. This may be helpful for you: I handle changing the endpoint from /api/v1 to /api/public/v1 by setting the api_version attribute in the DAG, but I am still facing a 404 response from Airbyte.
After a few tests, it seems that the Airbyte server doesn’t handle a request from Docker to Docker the same way it does from the host machine to Docker.
Additionally, I suggest you make sure both Docker containers are in the same network; take a look at the screenshots.
This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want
to access the original thread.