NextJS v13.4.16 does not work in docker container

[JurajKavka]

Verify canary release

• I verified that the issue exists in the latest Next.js canary release

Provide environment information

 Operating System:
      Platform: linux
      Arch: x64
      Version: #1 SMP PREEMPT_DYNAMIC Fri, 11 Aug 2023 11:03:36 +0000
    Binaries:
      Node: 18.16.0
      npm: 9.5.1
      Yarn: 1.22.19
      pnpm: N/A
    Relevant Packages:
      next: 13.4.16
      eslint-config-next: N/A
      react: 18.2.0
      react-dom: 18.2.0
      typescript: N/A
    Next.js Config:
      output: standalone

Which area(s) of Next.js are affected? (leave empty if unsure)

No response

Link to the code that reproduces this issue or a replay of the bug

https://github.com/vercel/next.js/blob/canary/examples/with-docker/README.md

To Reproduce

• Follow the instructions here: https://github.com/vercel/next.js/blob/canary/examples/with-docker/README.md
• be sure you have Next v13.4.16

Describe the Bug

Docker container with Next app starts but do not serve any content

Expected Behavior

Docker container should start and serve application

Which browser are you using? (if relevant)

No response

How are you deploying your application? (if relevant)

Google Clound

[DuCanhGH]

Can you try changing ENV HOSTNAME localhost to ENV HOSTNAME 0.0.0.0, or ENV HOSTNAME ::? Next now listens on localhost, rather than 0.0.0.0, when HOSTNAME is set to localhost :) Perhaps the Dockerfile should be updated.

[MegaOleh2]

add Labels area: examples

[MegaOleh2]

inside Dockerfile

Can you try changing ENV HOSTNAME localhost to ENV HOSTNAME 0.0.0.0, or ENV HOSTNAME ::? Next now listens on localhost, rather than 0.0.0.0, when HOSTNAME is set to localhost :) Perhaps the Dockerfile should be updated.

This is work thanks
You can check https://nodejs.org/en/docs/guides/nodejs-docker-webapp#create-the-nodejs-app
and https://bobcares.com/blog/connection-reset-by-peer-docker-error/

[michalvadak]

This is broken from 13.4.13

[michalvadak]

@timneutkens Wouldn't your fix fallback to Docker's default HOSTNAME env which is the ID of the container?

[timneutkens]

@michalvadak I verified the application runs correctly when removing the HOSTNAME env var:

The reason this was set explicitly before is that there was a bug with IPv6 handling, if the hostname docker assigns was IPv6 instead of IPv4 Next.js wouldn't function correctly, that was fixed in the latest stable release thanks to @DuCanhGH, so now the HOSTNAME env var is no longer required by default 👍

[DuCanhGH]

@timneutkens you may want to update other Docker examples as well 0084166 :)

[nguaman]

Hello,
Just FYI.

If I remove 'ENV HOSTNAME 0.0.0.0', it doesn't work on Google Cloud Run.

[DuCanhGH]

@nguaman sounds like Google Cloud Run doesn't provide HOSTNAME, perhaps a note with a commented out ENV HOSTNAME 0.0.0.0 should be added :)

[mhm13dev]

@DuCanhGH
When I try to deploy my code in a docker container with standalone mode using 13.3.4, the code is built and runs successfully.

But now I upgraded to 13.4.19 and the code is built successfully but I get this error when the container is started.

I am deploying it on AWS ECS

[DuCanhGH]

@mhm13dev that doesn't even look like a proper hostname 💀 Can you try ENV HOSTNAME 0.0.0.0?

[mhm13dev]

I tried these 3 values: 0.0.0.0, localhost, ::

None of them worked.

[mhm13dev]

I think this hostname is given by AWS ECS

[DuCanhGH]

@mhm13dev if 0.0.0.0 doesn't work then I don't really know either :( I have no experience with AWS ECS as well, so I can't tell why the hostname looks like that. Doesn't look like my PR is related as it just fixes issues with IPv6, whereas this hostname most likely isn't one. You know, going from 13.3.4 to 13.4.19 is quite a jump and a lot has changed since then. Perhaps you should consider opening a separate issue.

[mhm13dev]

@DuCanhGH sure thank you.

[github-actions]

This closed issue has been automatically locked because it had no new activity for 2 weeks. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.