EAI_AGAIN with latest postgresql:14 image

[sdawes437]

Name and Version

bitnami/postgresql:14

What architecture are you using?

amd64

What steps will reproduce the bug?

• Use this image as a service container in Azure Pipelines and a main container with an image based off the node 18.19 image
• Run a series of SQL scripts against the database, using pg-pool package
• Receive error message below (hostname removed)

Error: getaddrinfo EAI_AGAIN ######
    at /__w/1/s/node_modules/pg-pool/index.js:45:11
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
  errno: -3001,
  code: 'EAI_AGAIN',
  syscall: 'getaddrinfo',
  hostname: ######
}

The config from the pipeline yaml file is below, with parts redacted

  containers:
    - container: pipeline
      image: ##### (based off node:18.19)
      endpoint: GCR Central

    - container: postgres
      image: bitnami/postgresql:14
      ports:
        - 5432:5432
      env:
        POSTGRESQL_PASSWORD: #####
        POSTGRESQL_USERNAME: #####
        POSTGRESQL_DATABASE: #####

The pipeline runs without issue with the config below

  containers:
    - container: pipeline
      image: ##### (based off node:18.19)
      endpoint: GCR Central

    - container: postgres
      image: bitnami/postgresql:14.17.0-debian-12-r3
      ports:
        - 5432:5432
      env:
        POSTGRESQL_PASSWORD: ####
        POSTGRESQL_USERNAME: ####
        POSTGRESQL_DATABASE: ####

What is the expected behavior?

All scripts run without issue.

What do you see instead?

Error: getaddrinfo EAI_AGAIN ######
    at /__w/1/s/node_modules/pg-pool/index.js:45:11
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
  errno: -3001,
  code: 'EAI_AGAIN',
  syscall: 'getaddrinfo',
  hostname: ######
}

Additional information

I can't see any obvious changes in the version change that has caused this issue, however, I have run this multiple times with both postgreql images, to rule out that this is an intermittent issue with Azure Pipelines. The previous version succeeds, while the updated version (i.e. bitnami/postgresql:14.17.0-debian-12-r4) fails.

[carrodher]

Hi, the issue may not be directly related to the Bitnami container image/Helm chart, but rather to how the application is being utilized, configured in your specific environment, or tied to a particular scenario that is not easy to reproduce on our side.

If you think that's not the case and would like to contribute a solution, we'd like to invite you to create a pull request. The Bitnami team is excited to review your submission and offer feedback. You can find the contributing guidelines here.

Your contribution will greatly benefit the community. Please don't hesitate to contact us if you have any questions or need help.

Suppose you have questions about the application, customizing its content, or using technology and infrastructure. In that case, we strongly recommend that you consult the forums and user guides provided by the project responsible for the application or technology.

With that said, we'll keep this ticket open until the stale bot automatically closes it, in case someone from the community contributes valuable insights.

[github-actions]

This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.

[github-actions]

Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.