Hi, everyone! I'm new with Airbyte. why this happe...
# announcements
r
Hi, everyone! I'm new with Airbyte. why this happen to me. im using centos 7
m
Hi Robait!
how long have you waited?
the API takes up to 30 seconds to start
can you show the result of
docker ps | grep airbyte
r
It's been 1 minute
m
unexpected indeed
do you have the docker-compose logs available?
r
image.png
wait
is this?
image.png
m
are you not seeing:
Copy code
airbyte-server |     ___    _      __          __
airbyte-server |    /   |  (_)____/ /_  __  __/ /____
airbyte-server |   / /| | / / ___/ __ \/ / / / __/ _ \
airbyte-server |  / ___ |/ / /  / /_/ / /_/ / /_/  __/
airbyte-server | /_/  |_/_/_/  /_.___/\__, /\__/\___/
airbyte-server |                     /____/
airbyte-server | --------------------------------------
airbyte-server |  Now ready at <http://localhost:8000/>
airbyte-server | --------------------------------------
you are.. I can see it in the logs
do you want to jump on a quick call?
r
image.png
yes im see it
m
are you running it on your workstation?
r
yes, in my vps
centos 7
m
how are you connecting to the ui, which url are you using?
r
m
in the .env file, can you update:
Copy code
API_URL=<http://localhost:8001/api/v1/>
to:
API_URL=<http://209.126.10.254:8001/api/v1/>
r
ok i will try
m
once you've done it you will need to run:
Copy code
docker-compose down && docker-compose up
(restart the app)
r
work great sir.. thank for the advance
๐Ÿ™๐Ÿ˜˜
m
Yay! you're welcome. It should have worked out of the box. We might have changed something
@charles didn't artem do something so we automatically use the webapp hostname for the API?
it is possible that we broke it by hardcoding the env variable in
.env
c
previously when API_URL was not explicitly set it fell back on the webapp hostname using this
but we are now always setting the API_URL.
m
that was my intuition
c
@Jared Rhizor (Airbyte) did we need to add the API_URL in this commit. or would it be safe to remove it? looks like it was done to handle k8s configuration.
j
You can remove it from docker-compose env files. Iโ€™ll have to test that itโ€™s working in kube to remove it from those env files.
h
Robait - were you able to get airbyte working in your centos environ? i have it as well, but the docker image seems to be failing when the container itself tries to run docker commands - though I am able to run docker commands fine in the centos vm