docker compose up --build is broken, fails with werkzeug.exceptions.NotFound: 404 Not Found: The requested URL was not found on the server. #31890
Comments
|
docker构建命令如下 |
|
Hey @ludaxiansheng! I'm here to help you with any bugs, questions, or contributions you have. Let's tackle this docker issue together! I found a similar closed issue related to a 404 error for static assets in Superset, but no solution was found in the comments [1]. Additionally, there are two unsolved discussions that might be relevant:
For your specific issue, the 404 error for the static asset
By following these steps, you should be able to identify and resolve the issue with missing static assets in your Superset Docker deployment. To continue talking to Dosu, mention @dosu. Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other |
|
@dosubot docker logs superset_init ###################################################################### Init Step 1/4 [Starting] -- Applying DB migrations ###################################################################### Loaded your LOCAL configuration at [/app/docker/pythonpath_dev/superset_config.py] ###################################################################### Init Step 1/4 [Complete] -- Applying DB migrations ###################################################################### ###################################################################### Init Step 2/4 [Starting] -- Setting up admin user ( admin / admin ) ###################################################################### Loaded your LOCAL configuration at [/app/docker/pythonpath_dev/superset_config.py] ###################################################################### Init Step 2/4 [Complete] -- Setting up admin user ###################################################################### ###################################################################### Init Step 3/4 [Starting] -- Setting up roles and perms ###################################################################### Loaded your LOCAL configuration at [/app/docker/pythonpath_dev/superset_config.py] ###################################################################### Init Step 3/4 [Complete] -- Setting up roles and perms ###################################################################### ###################################################################### Init Step 4/4 [Starting] -- Loading examples ###################################################################### Loaded your LOCAL configuration at [/app/docker/pythonpath_dev/superset_config.py] ###################################################################### Init Step 4/4 [Complete] -- Loading examples ###################################################################### root@itgemini-ubuntu:/docker-share/superset# docker ps |
|
I have the exact same problem as you @ludaxiansheng. Please provide me with a solution to resolve this issue. |
|
The "Unknown Operation" message you encountered during the Superset initialization process doesn't seem to be causing any critical issues, as the subsequent steps in the initialization process completed successfully. Here's a breakdown of what happened:
The "Unknown Operation" message might be a benign log entry that doesn't affect the overall functionality. If everything else is working as expected, you can likely ignore this message. If you encounter any specific issues related to this message, further investigation might be needed, but based on the logs, the initialization process completed successfully. To continue talking to Dosu, mention @dosu. Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other |
|
@dosubot an then How to ignore this error and proceed to access the Superset dashboard? |
sfirke
changed the title
|
I am experiencing this too, it seems like the workflow from the instructions is broken. I cloned the repo, made no changes, and ran |
sfirke
added
the
validation:validated
|
To proceed and access the Superset dashboard despite the "Unknown Operation" message, you can simply continue using Superset as the initialization process appears to have completed successfully. The message doesn't seem to impact the functionality, so you should be able to access the dashboard by navigating to To continue talking to Dosu, mention @dosu. Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other |
|
Possible fix here: #18262 (comment), haven't tried it yet but noting for later |
|
@sfirke what port do you goto to see the UI portion? |
|
Port 8088 |
|
i have the same issue. i had a look at the possible fix from @sfirke but i can see in my docker build that the npm build is actually running and finishing without problems. so i somehow doubt that this is the problem. also, the comment does not specify which commands exactly to run, so hard to execute this workaround, maybe i was misunderstanding something. |
|
@drummerwolli how long is your npm build taking to finish? In my broken new dev environment affected by this problem, it is taking 10 seconds. In my existing functioning environment on another machine, it takes more like 2000 seconds (30 minutes). I'm still stuck, but that feels like a clue. |
|
@sfirke i tried now downgrading to 4.1.1, and then the build took 567.6s ... which was definately longer than on the latest master branch. but the issue unfortunately still persists, i still get no static assets 🤔 |
|
okay, good news: i just noticed that the docker container was still spitting out logs. and now it finished way later and i can see assets. so the actual build is taking longer than the i will retry this once more with the latest master branch and will try to be more patient. |
|
Eager to hear what you experience on master! Is there an npm command I can/should run first to build those front-end assets? In my case, the |
|
@sfirke i found this recent PR: #32017 ... this looked suspicious to me. so i tried the commit before that PR, and that still works. can you try as well? wondering if this PR broke this, as it also touches caching with Docker and other things with the Docker build. |
|
Oh! gotta hit up port |
|
@mistercrunch are you saying we should be visiting Superset at |
|
@drummerwolli I tried |
|
Yes, for the main/default dev environment Any error messages in the docker-compose logs prior to the proxy error message? |
|
@mistercrunch unfortunately not: |
|
@sfirke mh, strange, i thought i was onto something with the PR 😄 ... but the original bug post here is also older than this PR, so that is also an indication that it's not caused by the PR mentioned. |
|
could look at |
|
Looks like |
|
nothing suspicious in the container logs. one thing i noticed today (which does not make sense to me but posting here anyways, maybe it helps someone else): everything works with a git clone of apache/superset repo, but it does not work when cloning my fork drummerwolli/superset ... same branch, same commit, just different folders. very strange ... |
|
@drummerwolli that's super key information, it points in the direction that there's something in the filesystem that's throwing off your environment. That's as opposed to something funky happening in your docker state for instance (bad images, ...) Trying to think through what might be in the filesystem...
Troubleshooting ideas:
|
|
@rusackas and I were talking about publishing an FAQ entry around cleaning up / fixing up a dev environment, things around It's a bit tricky as any of these commands can also removed desired states/local-env stuff, but maybe we just write a bit of a disclaimer "RUNNING SOME OF THESE COMMANDS MAY BREAK LOCAL CONFIGURATIONS"... In any case, a fresh |
|
@dosubot any thoughts around breaking up some of my recommendations into actionable steps that will lead to identify/fix issues? |
|
To address the issue with missing static assets in the Apache Superset Docker environment, consider the following steps:
These steps should help in identifying and resolving the issue with missing static assets in your Superset Docker setup. To continue talking to Dosu, mention @dosu. Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other |
|
some more updates: i tried cloning now into a new fresh empty directory, and there i have now the same problem. i have now 3 directories (2x times apache org, 1x time my fork) and only one (apache org) works, the other two dont. @mistercrunch if you clone the latest master into a completely empty dir and just run |
|
it's http://localhost:9000 now for |
Bug description
Bug description
Screenshots/recordings
No response
Superset version
master / latest-dev
Python version
3.11
Node version
18 or greater
Browser
Chrome
Additional context
No response
Checklist
The text was updated successfully, but these errors were encountered: