aws / aws/aws-codebuild-docker-images

EMFILE and EBUSY errors in node 20

Open
#686 3 comments 2 reactions 0 assignees View on GitHub
Dominant language
Dockerfile
Stars
1.2k
Forks
971
Avg merge
2h 47m
Merged PRs (30d)
1

Description

**Describe the bug**
When switching from node 18 to node 20 we noticed a lot of EMFILE and EBUSY that we never had before.

**To Reproduce**
This is really hard to reproduce it only happens sometimes when making network requests.

**Expected behavior**
No error to appear

**Logs**
```JSON
{"errorType":"Error","errorMessage":"getaddrinfo EBUSY track-eu.customer.io","code":"EBUSY","errno":-16,"syscall":"getaddrinfo","hostname":"track-eu.customer.io","stack":["Error: getaddrinfo EBUSY track-eu.customer.io"," at __node_internal_captureLargerStackTrace (node:internal/errors:497:5)"," at __node_internal_ (node:internal/errors:716:10)"," at GetAddrInfoReqWrap.onlookupall [as oncomplete] (node:dns:118:26)"]}
```
```JSON
{"status":"error","message":"datadog:Failed to flush extension. connect EMFILE 127.0.0.1:8124 - Local (undefined:undefined)"}
```

**Platform (please complete the following information):**
node20 x86_64

**Additional context**
Not sure if this an issue with the image or the lambda runtime so please let me know if another repo makes more sense

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.