Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Lasted version of Nuxt not able to run in a container
See original GitHub issueEnvironment
~/website$ npx nuxi info Nuxt CLI v3.0.0-27415326.3c563fa 18:46:07 RootDir: /home/xxxx/website 18:46:08 Nuxt project info: 18:46:08
- Operating System: Linux
- Node Version: v16.14.2
- Nuxt Version: 3.0.0-27415326.3c563fa
- Package Manager: npm@8.5.0
- Bundler: Vite
- User Config: -
- Runtime Modules: -
- Build Modules: -
Reproduction
If a project with one of the latest versions of nuxt is built and containerized into a docker container, the server will not be accessible. But if you use an older version of Nuxt, keeping everything the same will not happen. for example 3.0.0-27389502.88da719 it run with no problem.
Describe the bug
The build server is not listening/responding to any call.
Additional context
The latest version of docker is been used, on a Linux server and on WSL.
Logs
No error logs are printed, it looks like everything is ok from the LOGs.
Issue Analytics
- State:
- Created a year ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
The environment variable to set is now
NITRO_HOSTorHOST, documented at https://nitro.unjs.io/deploy/node.html#environment-variables.Hello Daniel, yes, it was, maybe it is a good idea to change the documentation from nuxt because I got confused here.