gebhardtr opened a new issue, #21972:
URL: https://github.com/apache/superset/issues/21972
A clear and concise description of what the bug is.
#### How to reproduce the bug
1. Run `docker-compose up`
### Expected results
All containers are created without error
### Actual results
```
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '[email protected]',
npm WARN EBADENGINE required: { node: '^16.9.1', npm: '^7.5.4' },
npm WARN EBADENGINE current: { node: 'v16.18.0', npm: '8.19.2' }
npm WARN EBADENGINE }
```
what actually happens.
#### Screenshots
If applicable, add screenshots to help explain your problem.
### Environment
(please complete the following information):
- browser type and version: N/A
- superset version: commit `efefb66c2de15b66af0c18a2e70910e29ce9447c`
- python version: 3.9.15
- node.js version: 16.18.0
- any feature flags active:
### Checklist
Make sure to follow these steps before submitting your issue - thank you!
- [x] I have checked the superset logs for python stacktraces and included
it here as text if there are any.
- [x] I have reproduced the issue with at least the latest released version
of superset.
- [x] I have checked the issue tracker for the same issue and I haven't
found one similar.
https://github.com/apache/superset/issues/18615 appears to be related, but
it's larger in scope than this issue.
### Additional context
Add any other context about the problem here.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
