Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

superset-websocket Error #16432

Closed
2 of 3 tasks
j0narch3r opened this issue Aug 24, 2021 · 8 comments
Closed
2 of 3 tasks

superset-websocket Error #16432

j0narch3r opened this issue Aug 24, 2021 · 8 comments
Labels
#bug Bug report inactive Inactive for >= 30 days

Comments

@j0narch3r
Copy link

A clear and concise description of what the bug is.

Expected results

Running docker-compose up on a clean clone of Superset will launch the app

Actual results

  • I need to register the Snowflake driver for my use case which appears to require docker-compose up after adding the snowflake sqlalchemy driver to ./requirements-local.txt

  • Superset will run when using docker-compose-non-dev.yml as described here but not when running docker-compose up.

  • Instead what happens is I get superset-websocket Error (see screenshot) which leads to other errors and eventual failure

  • This is also on a fresh install of Docker for Mac

Screenshots

image

How to reproduce the bug

  1. Install Docker for Mac
  2. Follow instructions here
  3. Run docker-compose up

Environment

(please complete the following information):

  • superset version: superset version -bash: superset: command not found (but I cloned it two days ago)
  • python version: python --version Python 3.7.4
  • node.js version: node -v v16.7.0
  • any feature flags active:

Checklist

Make sure to follow these steps before submitting your issue - thank you!

  • I have checked the superset logs for python stacktraces and included it here as text if there are any.
  • I have reproduced the issue with at least the latest released version of superset.
  • I have checked the issue tracker for the same issue and I haven't found one similar.

Additional context

Add any other context about the problem here.

@j0narch3r j0narch3r added the #bug Bug report label Aug 24, 2021
@nytai
Copy link
Member

nytai commented Aug 24, 2021

You shouldn't need the superset-websocket service unless you plan to configure global async queries. You can probably just comment that out in your docker-compose file. Looks like your error is related to being able to reach the npm registry from your computer.

@j0narch3r
Copy link
Author

@nytai Ok good to know. I can try commenting that out. I have no problem installing from npm in general, and EAI_AGAIN at the end apparently suggests a network issue. Do you have any advice for reaching the npm registry from within docker? I ran through suggested steps here for a similar sounding case, but no luck so far:

moby/moby#32106

@stale
Copy link

stale bot commented Apr 18, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. For admin, please label this issue .pinned to prevent stale bot from closing the issue.

@rusackas
Copy link
Member

Closing this as stale, but @j0narch3r if you are still facing any issues here, we'll be happy to re-open it.

@JumayevIU
Copy link

Hello, I don't fix this bug on last version branch master
please help me
=> ERROR [superset-websocket build 4/4] RUN npm ci && npm run build 6.0s

[superset-websocket build 4/4] RUN npm ci && npm run build:

@JumayevIU
Copy link

photo_2024-01-06_16-11-07

@JumayevIU
Copy link

Hi help me

@l3v1k
Copy link

l3v1k commented Feb 23, 2024

@IlhomJumayevUrish i was able to run compose by changing superset-websocket/Dockerfile, replacing lines to explicitly use node arm64 version

FROM arm64v8/node:16-alpine as build
...
FROM arm64v8/node:16-alpine

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
#bug Bug report inactive Inactive for >= 30 days
Projects
None yet
Development

No branches or pull requests

5 participants