blue-santa commented on issue #30663:
URL: https://github.com/apache/superset/issues/30663#issuecomment-3038290839
I'm running into this issue currently.
Running on OpenMandriva Rock 6.0 x86_64 x11
Earlier tonight, this was not an issue. I was having connectivity issues
within the docker container and was troubleshooting with the help of Gemini AI.
I changed the `/etc/docker/daemon.json` file to allow for some dns
resolution, as recommended by the ai bot.
```
{
"dns": ["192.168.1.1", "8.8.8.8", "8.8.4.4", "208.67.222.222",
"208.67.220.220"],
"dns-opts": ["ndots:0"]
}
```
I also changed the `.db` section of `docker-compose.yml` as follows. (I
changed port to `5433` previously to deal with my existing postgresql
installation.)
```
db:
env_file:
- path: docker/.env # default
required: true
- path: docker/.env-local # optional override
required: false
image: postgres:16
container_name: superset_db
restart: unless-stopped
ports:
- "127.0.0.1:5433:5432"
volumes:
- db_home:/var/lib/postgresql/data
- ./docker/docker-entrypoint-initdb.d:/docker-entrypoint-initdb.d
dns:
- 192.168.1.1
- 8.8.8.8
- 8.8.4.4
- 208.67.222.222
- 208.67.220.220
```
Suddenly, the issue appeared.
```
npm WARN EBADENGINE Unsupported engine {
package: '@typescript-eslint/[email protected]',
required: { node: '^18.18.0 || ^20.9.0 || >=21.1.0' },
current: { node: 'v16.20.2', npm: '8.19.4' }
}
```
Gemini AI recommended changing `.../superset/superset-websocket/Dockerfile`
as follows
```
# ... (header comments) ...
FROM node:20-alpine AS build
WORKDIR /home/superset-websocket
COPY . ./
RUN npm ci && \
npm run build
FROM node:20-alpine
# ... (rest of the Dockerfile) ...
```
This resulted in an inverse error.
```
npm warn EBADENGINE Unsupported engine {
package: '[email protected]',
required: { node: '^16.9.1', npm: '^7.5.4 || ^8.1.2' },
current: { node: 'v20.19.3', npm: '10.8.2' }
}
```
Before this error appeared, superset only once successfully built the
backend, but never successfully built the front end.
--
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]
