Fargate Docker - cannot connect or ping the task that uses internal IP

0

Hi, I have set up a public subnet in AWS Fargate ECS (on linux platform) to run a public docker for setting up a 'Jamulus' server. Jamulus seems to be starting ok according to the AWS log it produces, but I cannot connect from the Jamulus client.

Looking into this, in AWS the task is assigned: Public IP 16.171.60.xxx Private IP 10.0.7.124

The Jamulus log (in AWS) states: 2022-10-07 xx.xx.xx | Using "10.0.7.124" as external IP. 2022-10-07 xx.xx.xx | - Starting in server mode by default (due to compile time option) 2022-10-07 xx.xx.xx | No GUI support compiled. Running in headless mode.

Using the local IP as external seems like a source for the problem, but I cannot find any way to set the external IP as primary. I cannot ping the service, and I have opened Security group for all traffic to try to get some connectivity. Since the tasks starts up I assume the image is retreived from internet.

Thanks!

asked 2 years ago60 views
No Answers

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions