Even if I progress beyond that and try to add a co...
# contributing-to-airbyte
m
Even if I progress beyond that and try to add a connector internally, still no luck. Infinite wait. No matter the connector.
u
did you have a previous version already installed?
u
or are you starting literally from scratch?
u
Yep. I did have 0.14.0-alpha installed.
u
I did a docker system prune -a
u
Also docker volume prune
u
is there a reason that you're going to 0.17.2-alpha as opposed to 0.17.3-alpha?
u
Newp! Only that the last time I checked, the version was 0.17.2
u
Let me try 0.17.3
u
Same situation
u
do the logs show anything?
u
docker ps
to get the container id of the server
u
then
u
docker logs <container id>
u
Sending
u
Any idea what the issue might be?
u
Copy code
2021-03-25 03:48:14 [33mWARN[m i.t.i.c.GrpcRetryer(retryWithResult):152 - {workspace_app_root=/tmp/workspace/server/logs} - Retrying after failure
io.grpc.StatusRuntimeException: UNAVAILABLE: Unable to resolve host airbyte-temporal
u
this error seems to be the source of your problems.
u
what operating system are you rrunning on?
u
Ubuntu 20.04 LTS
u
can you share what happens when you run docker ps?
u
Copy code
CONTAINER ID        IMAGE                            COMMAND                  CREATED             STATUS              PORTS                    
          NAMES
bda3ec420668        airbyte/server:0.17.3-alpha      "/bin/bash -c './wai…"   19 minutes ago      Up 19 minutes       8000/tcp, 0.0.0.0:8001->8
001/tcp   airbyte-server
baacc2eb1752        airbyte/db:0.17.3-alpha          "docker-entrypoint.s…"   19 minutes ago      Up 19 minutes       5432/tcp                 
          airbyte-db
fda16428fd14        airbyte/webapp:0.17.3-alpha      "/docker-entrypoint.…"   19 minutes ago      Up 19 minutes       0.0.0.0:8000->80/tcp     
          airbyte-webapp
78150ba49d57        airbyte/scheduler:0.17.3-alpha   "/bin/bash -c './wai…"   19 minutes ago      Up 19 minutes                                
          airbyte-scheduler
u
Maybe this is an old version of the docker-compose file?
u
Well… I’ll be.
u
okay. so the problem here is that there should be another container running.
u
how did you upgrade?
u
I only ever had a docker-compose file.
u
I never cloned the repo.
u
got it.
u
I simply copied that from github.
u
well you definitely need the updated docker-compose file.
u
Now, I’ll actually clone the full repo.
u
so when you upgraded you were just bumping the version in the .env file? or in an env variable?
u
Yep.,
u
makes sense!
u
Cloned the full repo. Now, I’ll update my repo when I upgrade. 🙂
u
Yep. All works now.
u
Thanks for your help! I totally forgot that I did this.