docker-compose up and can't open the UI

hantmac commented 1 year ago

A clear and concise description of what the bug is.

How to reproduce the bug

According this doc

git clone
cd superset
touch ./docker/requirements-local.txt and echo clickhouse-connect > ./docker/requirements-local.txt
docker-compose up

Expected results

Open the superset in browser.

Actual results

Can not open superset in browser like this:

Screenshots

Environment

(please complete the following information):

browser type and version: Chrome
superset version: the newest code
python version: python3.9
node.js version: v14.19.3

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.

Additional context

werkzeug.exceptions.NotFound: 404 Not Found: The requested URL was not found on the server. If you entered the URL manually please check your spelling and try again.
superset_app             | 172.19.0.1 - - [08/Mar/2023 01:11:59] "GET /static/assets/images/favicon.png HTTP/1.1" 404 -
superset_app             | 2023-03-08 01:11:59,855:INFO:werkzeug:172.19.0.1 - - [08/Mar/2023 01:11:59] "GET /static/assets/images/favicon.png HTTP/1.1" 404 -
superset_worker_beat     | [2023-03-08 01:12:00,094: INFO/MainProcess] Scheduler: Sending due task reports.scheduler (reports.scheduler)
superset_worker          | [2023-03-08 01:12:00,174: INFO/MainProcess] Task reports.scheduler[3626bbb8-062a-49e7-8f2a-033ed05decf9] received
superset_worker          | [2023-03-08 01:12:00,632: INFO/ForkPoolWorker-3] Task reports.scheduler[3626bbb8-062a-49e7-8f2a-033ed05decf9] succeeded in 0.4056195000000571s: None
superset_app             | 2023-03-08 01:12:00,899:WARNING:superset.views.base:HTTPException
superset_app             | Traceback (most recent call last):
superset_app             |   File "/usr/local/lib/python3.8/site-packages/flask/app.py", line 1517, in full_dispatch_request
superset_app             |     rv = self.dispatch_request()
superset_app             |   File "/usr/local/lib/python3.8/site-packages/flask/app.py", line 1503, in dispatch_request
superset_app             |     return self.ensure_sync(self.view_functions[rule.endpoint])(**req.view_args)
superset_app             |   File "/usr/local/lib/python3.8/site-packages/flask/app.py", line 509, in <lambda>
superset_app             |     view_func=lambda **kw: self_ref().send_static_file(**kw),  # type: ignore # noqa: B950
superset_app             |   File "/usr/local/lib/python3.8/site-packages/flask/scaffold.py", line 322, in send_static_file
superset_app             |     return send_from_directory(
superset_app             |   File "/usr/local/lib/python3.8/site-packages/flask/helpers.py", line 676, in send_from_directory
superset_app             |     return werkzeug.utils.send_from_directory(  # type: ignore
superset_app             |   File "/usr/local/lib/python3.8/site-packages/werkzeug/utils.py", line 586, in send_from_directory
superset_app             |     raise NotFound()
superset_app             | werkzeug.exceptions.NotFound: 404 Not Found: The requested URL was not found on the server. If you entered the URL manually please check your spelling and try again.

woozhijun commented 1 year ago

The same problem.

matiasomartin commented 1 year ago

The same problem.

artrusx commented 1 year ago

i'm having this same issue

matiasomartin commented 1 year ago

I'm having te same problem.

vitali-melnyk commented 1 year ago

The same issue. Can't start in docker-compose

zajcomm commented 1 year ago

same here... any hits on what to do?

ningaro commented 1 year ago

I also faced with such problem, but deleting the old node_modules folders helped in my case. You may use one of this commands:

git clean -xdf
git reset --hard <- 🛑 DANGER, COMMIT LOCAL CHANGES BEFORE!

bukem commented 1 year ago

Looks like the problem is caused by permissions to node_modules folder. It is owner by root, not by user used to run superset. Changing the ownership fixed the issue for me. Actually, I changed it for all the files:

chown -R myuser:mygroup /path_to_superset

Mloweedgar commented 7 months ago

node_modules

@bukem thank you your solution works, also for lazy people like me :) they can also try:

chmod -v -R 777 node_modules/

tmnvanderberg commented 6 months ago

Having the same issue, none of the proposed solutions work for me... :(

rusackas commented 5 months ago

The original report is using node 14. Can you try with node 16? We're actually going to be on node 18 imminently, and moving to 20, so 14 is probably old enough to be quite problematic.

UsenPang commented 4 months ago

I have the same issue,you may need to wait a bit, after starting superset_node there are some packages to download.

Emily0330 commented 3 days ago

For me, follow the QuickStart guide and type docker compose -f docker-compose-image-tag.yml up rather than just docker compose up solves the problem!

apache / superset