Hi all. I'm working on a AWS ECS Fargate deploymen...
# all-things-deploymentd
damp-solstice-31196
03/13/2024, 7:47 PMHi all. I'm working on a AWS ECS Fargate deployment and have stumbled on an issue I can't figure out. I have an RDS MySQL database and am deploying all other services as containers. The containers I've successfully brought up are the following:
• zookeeper
• elasticsearch
• elasticsearch-setup
• kafka-setup
• broker
• schema-registry
• datahub-upgrade
I'm stuck on datahub-gms with an error about the Jetty server and failing to bind to 0.0.0.0/0.0.0.0:8080. There are no other containers using port 8080. I also attempted using a different port (8082) and got the same error, so it seems like an issue internal to the container. Attaching additional info on error message, settings in the thread.
damp-solstice-31196
03/13/2024, 7:49 PMHere is where I see the error
Failed to bind to 0.0.0.0/0.0.0.0:8080damp-solstice-31196
03/13/2024, 7:53 PMHere are the environment variables after removing the RDS info. Basically the defaults except I used localhost instead of the container names that come with the quickstart package since AWS ECS Fargate lets you communicate over localhost in this way.
damp-solstice-31196
03/13/2024, 7:55 PMI'm deploying using Terraform and the port mapping settings for the container are like so:
damp-solstice-31196
03/13/2024, 8:08 PMDocker platform is linux/arm64.
damp-solstice-31196
03/13/2024, 8:13 PMDatahub version is v0.12.1.
b
billions-tailor-78534
03/14/2024, 10:04 PMWhat's the network mode being used?
d
damp-solstice-31196
03/14/2024, 10:04 PMawsvpc
damp-solstice-31196
03/14/2024, 10:04 PMIt's the default/only option for Fargate
b
billions-tailor-78534
03/14/2024, 10:07 PMYou sure there's no other container binding on that port?
d
damp-solstice-31196
03/14/2024, 10:08 PMI've checked multiple times, only my service is running on this cluster, and 8080 is used only for this container.
damp-solstice-31196
03/14/2024, 10:09 PMAlso when I tried with 8082, it still gave me the error with 8080 in it, not 8082.
damp-solstice-31196
03/14/2024, 10:09 PMThat might not have been clear on my earlier message, my bad
b
billions-tailor-78534
03/14/2024, 10:10 PMI mean, it's not about the service. In awsvpc mode, it looks like a task can have multiple containers. Since you are using localhost, that seems to be the case.
billions-tailor-78534
03/14/2024, 10:11 PMI would try maybe not starting gms, but keep the port mapping, and check if you can access anything on port 8080
d
damp-solstice-31196
03/14/2024, 10:12 PMI can give that a try
damp-solstice-31196
03/14/2024, 10:13 PMThanks, I'll update tomorrow if I find anything interesting