Hi Trying Dockerised Datahub in AWS env, as <@U026...
# all-things-deployment
h
Hi Trying Dockerised Datahub in AWS env, as @blue-holiday-20644 suggested. Using Postgres instead of mysql. Getting this error - Trying the above with postgres rather than mysql- unfortunately getting this - Any suggestions?
l
@early-lamp-41924 ^
e
Can you check the logs of these containers? Seems like schema-registry and mysql containers didn’t start up
h
I see this error in gms container @7l0c3p9nh - Internal server error, for (POST) [/api/v2/graphql] -> play.api.UnexpectedException: Unexpected exception[CompletionException: java.net.ConnectException: Connection refused: datahub-gms/172.18.0.10:8080] at play.api.http.HttpErrorHandlerExceptions$.throwableToUsefulException(HttpErrorHandler.scala:247) at play.api.http.DefaultHttpErrorHandler.onServerError(HttpErrorHandler.scala:176) at play.core.server.AkkaHttpServer$$anonfun$2.applyOrElse(AkkaHttpServer.scala:363) at play.core.server.AkkaHttpServer$$anonfun$2.applyOrElse(AkkaHttpServer.scala:361)
@early-lamp-41924 - Also how do we run each docker image on an ecs cluster?
e
Can you run docker-compose commands?
I usually do something like this from local
Copy code
COMPOSE_DOCKER_CLI_BUILD=1 DOCKER_BUILDKIT=1 docker-compose -p datahub -f quickstart/docker-compose-without-neo4j.quickstart.yml up -d --no-deps datahub-gms
but for the above seems like gms is not the issue. gms doesn’t start up until kafka, mysql, and elasticsearch is up and ready
Seems like mysql not spinning up well is causing gms to stall and then timeout
h
unfortunately on the ecs cluster , we are able to only runs tasks using the docker image
e
interesting. so you put in the docker-compose files and ECS decides how to deploy?
h
No, I am using the docker compose file on an EC2 instance. Still trying to figure out how to deploy datahub on ECS
e
So the above is a message from the EC2 instance? Did you find out why mysql did not start up?
or are you using RDS instead of a local mysql instance here?
h
Yes, using RDS instance...
e
But you still have schema registry enabled in the docker-compose right?
Then please use the quickstart.sh (or just copy the command its running)
the datahub cli checks for existence of these containers, so doesnt match youre use case