Skip to content
By using AWS re:Post, you agree to the AWS re:Post Terms of Use
AWS re:Postre:Post
About re:Post

Fargate: DNS issues / no such host

1

Hi all.

We use Fargate and we are encountering random 'no such host' errors on our containers.

90% of the time all works well but randomly, for a hostname that resolved just fine seconds before, the request fails.

I'd try setting 1.1.1.1 as the resolver but since we're using VPC that does not work.

Anyone else seeing this? Workarounds?

Topics
Containers
Tags
Amazon Elastic Container Service
Language
English

asked 7 years ago1.3K views

1 Answer
1

Solved: Problem was that the process was running out of open file descriptors. DNS resolution was just . a symptom of that.

answered 7 years ago

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.

Relevant content