You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@superset.apache.org by "AFTABSHIAKH786 (via GitHub)" <gi...@apache.org> on 2026/03/05 07:31:34 UTC
[D] unable to setup using docker compose for 5.0.0 [superset]
GitHub user AFTABSHIAKH786 created a discussion: unable to setup using docker compose for 5.0.0
`Admin User admin created.
######################################################################
Init Step 2/4 [Complete] -- Setting up admin user
######################################################################
######################################################################
Init Step 3/4 [Starting] -- Setting up roles and perms
######################################################################
Traceback (most recent call last):
File "/app/.venv/bin/superset", line 4, in <module>
from superset.cli.main import superset
File "/app/superset/__init__.py", line 19, in <module>
from superset.app import create_app # noqa: F401
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/app/superset/app.py", line 39, in <module>
from superset.extensions.local_extensions_watcher import (
File "/app/superset/extensions/__init__.py", line 42, in <module>
from superset.async_events.async_query_manager import AsyncQueryManager
File "/app/superset/async_events/async_query_manager.py", line 32, in <module>
from superset.utils.core import get_user_id
File "/app/superset/utils/core.py", line 100, in <module>
from superset.sql.parse import sanitize_clause
File "/app/superset/sql/parse.py", line 48, in <module>
from superset.sql.dialects import DB2, Dremio, Firebolt, Pinot
File "/app/superset/sql/dialects/__init__.py", line 18, in <module>
from .db2 import DB2
ModuleNotFoundError: No module named 'superset.sql.dialects.db2'
Getting this error multiple time while starting a development setup. I am following the offical docs for the docker compose setup using the below command
docker compose up -d --build
GitHub link: https://github.com/apache/superset/discussions/38439
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] unable to setup using docker compose for 5.0.0 [superset]
Posted by "AFTABSHIAKH786 (via GitHub)" <gi...@apache.org>.
GitHub user AFTABSHIAKH786 added a comment to the discussion: unable to setup using docker compose for 5.0.0
<img width="1366" height="768" alt="image" src="https://github.com/user-attachments/assets/edf843d0-4fde-40f9-adc3-903cc7f0b2aa" />
I have followed the steps above and Now docker container were started but now I am having this on my screen. I am not able to find anything that causing this ?
GitHub link: https://github.com/apache/superset/discussions/38439#discussioncomment-16007712
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] unable to setup using docker compose for 5.0.0 [superset]
Posted by "dosubot[bot] (via GitHub)" <gi...@apache.org>.
GitHub user dosubot[bot] edited a comment on the discussion: unable to setup using docker compose for 5.0.0
<!-- Greeting -->
Hi @AFTABSHIAKH786! I'm [Dosu](https://go.dosu.dev/dosubot) and Iām helping the superset team.
<!-- Answer -->
This appears to be a version mismatch issue. The `superset.sql.dialects.db2` module [was added after the 5.0.0 release](https://github.com/apache/superset/pull/36365), so it doesn't exist in version 5.0.0 at all.
The error suggests your Docker setup might be pulling inconsistent code - possibly mixing newer source files with the 5.0.0 release. A few things to try:
1. **Clean rebuild**: Remove all cached images and volumes, then rebuild:
```bash
docker compose down -v
docker system prune -a
docker compose up -d --build
```
2. **Check your branch/tag**: Make sure you're on the correct `5.0.0` tag and not on `master` or a newer branch that has the dialects module reference but missing files.
3. **Use a newer release**: If you're okay with a more recent version, consider using the latest release where the `sql.dialects` module is fully implemented.
Also note that [Superset 5.0.0 switched from `pip` to `uv` for package management](https://github.com/apache/superset/issues/32364), so if you have any custom packages to install, you'll need to use `/app/.venv/bin/uv pip install` instead of regular pip.
Could you confirm which branch/tag you cloned and whether you made any modifications to the repo?
<!-- Dosu Comment Footer -->
*To reply, just mention [@dosu](https://go.dosu.dev/dosubot?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=reply-with-mention&utm_term=apache%2Fsuperset).*
---
Share context across your team and agents. Try [Dosu](https://dosu.dev?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-tagline&utm_term=apache%2Fsuperset).
[](https://app.dosu.dev/response-feedback?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-feedback&utm_term=apache%2Fsuperset&message_id=51c16af4-5721-4182-a027-0df61303c33c) [](https://github.dosu.com/apache/superset?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-learn-repo&utm_term=apache%2Fsuperset) [](https://app.dosu.dev/signup?referrer=openSource&source=github-footer&utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-add-team&utm_term=apache%2Fsuperset)
GitHub link: https://github.com/apache/superset/discussions/38439#discussioncomment-16006759
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] unable to setup using docker compose for 5.0.0 [superset]
Posted by "dosubot[bot] (via GitHub)" <gi...@apache.org>.
GitHub user dosubot[bot] edited a comment on the discussion: unable to setup using docker compose for 5.0.0
<!-- Answer -->
The 502 errors for static assets indicate [a race condition where nginx is trying to proxy requests to the webpack dev server, but the server isn't ready yet](https://github.com/apache/superset/pull/38161). This is a known issue - the `superset-node` container needs time to run `npm install` and start webpack, which [can take 10+ minutes](https://github.com/apache/superset/issues/31890#issuecomment-2644044130).
Check if the webpack dev server is running:
```bash
docker compose logs superset-node
```
Look for a message like `"webpack 5.x.x compiled successfully"`. If you don't see that yet, the build is still in progress.
Also, I notice you're accessing `http://localhost/superset/welcome/` - are you using a custom nginx configuration or reverse proxy? The default Docker dev setup serves on port 9000 directly (`http://localhost:9000`). If you have nginx in front, make sure it's configured to wait for the webpack server to be healthy before starting, or simply wait until the build completes.
If waiting doesn't help, try restarting just the node container after the other services are up:
```bash
docker compose restart superset-node
```
<!-- Dosu Comment Footer -->
*To reply, just mention [@dosu](https://go.dosu.dev/dosubot?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=reply-with-mention&utm_term=apache%2Fsuperset).*
---
Docs are dead. Just use [Dosu](https://dosu.dev?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=static-docs-tagline&utm_term=apache%2Fsuperset).
[](https://app.dosu.dev/response-feedback?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=static-docs-feedback&utm_term=apache%2Fsuperset&message_id=0178b0c1-f6e2-4c63-ab4a-3e8e27154305) [](https://github.dosu.com/apache/superset?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=static-docs-ask-repo&utm_term=apache%2Fsuperset) [](https://app.dosu.dev/signup?referrer=openSource&source=github-footer&utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=static-docs-share-team&utm_term=apache%2Fsuperset)
GitHub link: https://github.com/apache/superset/discussions/38439#discussioncomment-16007910
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] unable to setup using docker compose for 5.0.0 [superset]
Posted by "AFTABSHIAKH786 (via GitHub)" <gi...@apache.org>.
GitHub user AFTABSHIAKH786 edited a comment on the discussion: unable to setup using docker compose for 5.0.0
Now I am getting this in network tab
<img width="1366" height="768" alt="image" src="https://github.com/user-attachments/assets/bce31c84-e330-4e0e-aaa7-feade1ac2a7d" />
@dosu
GitHub link: https://github.com/apache/superset/discussions/38439#discussioncomment-16007830
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] unable to setup using docker compose for 5.0.0 [superset]
Posted by "dosubot[bot] (via GitHub)" <gi...@apache.org>.
GitHub user dosubot[bot] added a comment to the discussion: unable to setup using docker compose for 5.0.0
<!-- Answer -->
This is a [known issue with Superset Docker setups](https://github.com/apache/superset/issues/36311) - the blank page with broken images typically indicates frontend assets haven't loaded properly. A few things to check:
1. **Wait for frontend build**: The webpack build can take 5-10 minutes after containers start. Monitor progress with:
```bash
docker logs -f superset_app
```
2. **Check the port**: If you're using the dev `docker-compose.yml`, [try accessing `http://localhost:9000` instead of port 8088](https://github.com/apache/superset/issues/32898) - recent versions changed the default dev port.
3. **Check browser console**: Press F12 and look for 404 errors on `/static/assets/` paths - this confirms missing frontend assets.
If none of that helps, try a complete clean rebuild:
```bash
docker compose down -v
docker image prune -a
docker compose build
docker compose up
```
Then wait 5-10 minutes for the frontend build to complete before accessing the UI.
<!-- Dosu Comment Footer -->
*To reply, just mention [@dosu](https://go.dosu.dev/dosubot).*
---
<sup>How did I do? [Good](https://app.dosu.dev/response-feedback/3cdc6def-90d8-4b01-8927-5d0c16205399?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/3cdc6def-90d8-4b01-8927-5d0c16205399?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/3cdc6def-90d8-4b01-8927-5d0c16205399?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/3cdc6def-90d8-4b01-8927-5d0c16205399?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/3cdc6def-90d8-4b01-8927-5d0c16205399?feedback_type=hallucination) | [Report š](https://app.dosu.dev/response-feedback/3cdc6def-90d8-4b01-8927-5d0c16205399?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/3cdc6def-90d8-4b01-8927-5d0c16205399?feedback_type=other)</sup>
[](https://app.dosu.dev/a28d3c7e-a9d3-459e-9fb6-3a6f9ff4f357/ask?utm_source=github) [](https://cursor.com/link/prompt?text=This%20is%20a%20%5Bknown%20issue%20with%20Superset%20Docker%20setups%5D%28https%3A//github.com/apache/superset/issues/36311%29%20-%20the%20blank%20page%20with%20broken%20images%20typically%20indicates%20frontend%20assets%20haven%27t%20loaded%20properly.%20A%20few%20things%20to%20check%3A%0A%0A1.%20%2A%2AWait%20for%20frontend%20build%2A%2A%3A%20The%20webpack%20build%20can%20take%205-10%20minutes%20after%20containers%20start.%20Monitor%20progress%20with%3A%0A%20%20%20%60%60%60bash%0A%20%20%20docker%20logs%20-f%20superset_app%0A%20%20%20%60%60%60%0A%0A2.%20%2A%2ACheck%20the%20port%2A%2A%3A%20If%20you%27re%20using%20the%20dev%20%60docker-compose.yml%60%2C%20%5Btry%20accessing%20%60http%3A//localhost%3A9000%60%20instead%20of%20port%208088%5D%28https%3A//gi
thub.com/apache/superset/issues/32898%29%20-%20recent%20versions%20changed%20the%20default%20dev%20port.%0A%0A3.%20%2A%2ACheck%20browser%20console%2A%2A%3A%20Press%20F12%20and%20look%20for%20404%20errors%20on%20%60/static/assets/%60%20paths%20-%20this%20confirms%20missing%20frontend%20assets.%0A%0AIf%20none%20of%20that%20helps%2C%20try%20a%20complete%20clean%20rebuild%3A%0A%60%60%60bash%0Adocker%20compose%20down%20-v%0Adocker%20image%20prune%20-a%0Adocker%20compose%20build%0Adocker%20compose%20up%0A%60%60%60%0A%0AThen%20wait%205-10%20minutes%20for%20the%20frontend%20build%20to%20complete%20before%20accessing%20the%20UI.) [](https://go.dosu.dev/discord-bot) [](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/apache/superset/discussions/38439)
GitHub link: https://github.com/apache/superset/discussions/38439#discussioncomment-16007747
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] unable to setup using docker compose for 5.0.0 [superset]
Posted by "dosubot[bot] (via GitHub)" <gi...@apache.org>.
GitHub user dosubot[bot] edited a comment on the discussion: unable to setup using docker compose for 5.0.0
<!-- Answer -->
This is a [known issue with Superset Docker setups](https://github.com/apache/superset/issues/36311) - the blank page with broken images typically indicates frontend assets haven't loaded properly. A few things to check:
1. **Wait for frontend build**: The webpack build can take 5-10 minutes after containers start. Monitor progress with:
```bash
docker logs -f superset_app
```
2. **Check the port**: If you're using the dev `docker-compose.yml`, [try accessing `http://localhost:9000` instead of port 8088](https://github.com/apache/superset/issues/32898) - recent versions changed the default dev port.
3. **Check browser console**: Press F12 and look for 404 errors on `/static/assets/` paths - this confirms missing frontend assets.
If none of that helps, try a complete clean rebuild:
```bash
docker compose down -v
docker image prune -a
docker compose build
docker compose up
```
Then wait 5-10 minutes for the frontend build to complete before accessing the UI.
<!-- Dosu Comment Footer -->
*To reply, just mention [@dosu](https://go.dosu.dev/dosubot?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=reply-with-mention&utm_term=apache%2Fsuperset).*
---
Docs are dead. Just use [Dosu](https://dosu.dev?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=static-docs-tagline&utm_term=apache%2Fsuperset).
[](https://app.dosu.dev/response-feedback?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=static-docs-feedback&utm_term=apache%2Fsuperset&message_id=3cdc6def-90d8-4b01-8927-5d0c16205399) [](https://github.dosu.com/apache/superset?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=static-docs-ask-repo&utm_term=apache%2Fsuperset) [](https://app.dosu.dev/signup?referrer=openSource&source=github-footer&utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=static-docs-share-team&utm_term=apache%2Fsuperset)
GitHub link: https://github.com/apache/superset/discussions/38439#discussioncomment-16007747
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] unable to setup using docker compose for 5.0.0 [superset]
Posted by "dosubot[bot] (via GitHub)" <gi...@apache.org>.
GitHub user dosubot[bot] added a comment to the discussion: unable to setup using docker compose for 5.0.0
<!-- Greeting -->
Hi @AFTABSHIAKH786! I'm [Dosu](https://go.dosu.dev/dosubot) and Iām helping the superset team.
<!-- Answer -->
This appears to be a version mismatch issue. The `superset.sql.dialects.db2` module [was added after the 5.0.0 release](https://github.com/apache/superset/pull/36365), so it doesn't exist in version 5.0.0 at all.
The error suggests your Docker setup might be pulling inconsistent code - possibly mixing newer source files with the 5.0.0 release. A few things to try:
1. **Clean rebuild**: Remove all cached images and volumes, then rebuild:
```bash
docker compose down -v
docker system prune -a
docker compose up -d --build
```
2. **Check your branch/tag**: Make sure you're on the correct `5.0.0` tag and not on `master` or a newer branch that has the dialects module reference but missing files.
3. **Use a newer release**: If you're okay with a more recent version, consider using the latest release where the `sql.dialects` module is fully implemented.
Also note that [Superset 5.0.0 switched from `pip` to `uv` for package management](https://github.com/apache/superset/issues/32364), so if you have any custom packages to install, you'll need to use `/app/.venv/bin/uv pip install` instead of regular pip.
Could you confirm which branch/tag you cloned and whether you made any modifications to the repo?
<!-- Dosu Comment Footer -->
*To reply, just mention [@dosu](https://go.dosu.dev/dosubot).*
---
<sup>How did I do? [Good](https://app.dosu.dev/response-feedback/51c16af4-5721-4182-a027-0df61303c33c?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/51c16af4-5721-4182-a027-0df61303c33c?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/51c16af4-5721-4182-a027-0df61303c33c?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/51c16af4-5721-4182-a027-0df61303c33c?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/51c16af4-5721-4182-a027-0df61303c33c?feedback_type=hallucination) | [Report š](https://app.dosu.dev/response-feedback/51c16af4-5721-4182-a027-0df61303c33c?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/51c16af4-5721-4182-a027-0df61303c33c?feedback_type=other)</sup>
[](https://app.dosu.dev/a28d3c7e-a9d3-459e-9fb6-3a6f9ff4f357/ask?utm_source=github) [](https://cursor.com/link/prompt?text=This%20appears%20to%20be%20a%20version%20mismatch%20issue.%20The%20%60superset.sql.dialects.db2%60%20module%20%5Bwas%20added%20after%20the%205.0.0%20release%5D%28https%3A//github.com/apache/superset/pull/36365%29%2C%20so%20it%20doesn%27t%20exist%20in%20version%205.0.0%20at%20all.%0A%0AThe%20error%20suggests%20your%20Docker%20setup%20might%20be%20pulling%20inconsistent%20code%20-%20possibly%20mixing%20newer%20source%20files%20with%20the%205.0.0%20release.%20A%20few%20things%20to%20try%3A%0A%0A1.%20%2A%2AClean%20rebuild%2A%2A%3A%20Remove%20all%20cached%20images%20and%20volumes%2C%20then%20rebuild%3A%0A%20%20%20%60%60%60bash%0A%20%20%20docker%20compose%20down%20-v%0A%20%20%20docker%20system%20prune%20-a%0A%20%20%20docker%20compose%20up%20-d%20--build%0A%
20%20%20%60%60%60%0A%0A2.%20%2A%2ACheck%20your%20branch/tag%2A%2A%3A%20Make%20sure%20you%27re%20on%20the%20correct%20%605.0.0%60%20tag%20and%20not%20on%20%60master%60%20or%20a%20newer%20branch%20that%20has%20the%20dialects%20module%20reference%20but%20missing%20files.%0A%0A3.%20%2A%2AUse%20a%20newer%20release%2A%2A%3A%20If%20you%27re%20okay%20with%20a%20more%20recent%20version%2C%20consider%20using%20the%20latest%20release%20where%20the%20%60sql.dialects%60%20module%20is%20fully%20implemented.%0A%0AAlso%20note%20that%20%5BSuperset%205.0.0%20switched%20from%20%60pip%60%20to%20%60uv%60%20for%20package%20management%5D%28https%3A//github.com/apache/superset/issues/32364%29%2C%20so%20if%20you%20have%20any%20custom%20packages%20to%20install%2C%20you%27ll%20need%20to%20use%20%60/app/.venv/bin/uv%20pip%20install%60%20instead%20of%20regular%20pip.%0A%0ACould%20you%20confirm%20which%20branch/tag%20you%20cloned%20and%20whether%20you%20made%20any%20modifications%20to%20the%20repo%3F) [](https://go.dosu.dev/discord-bot) [](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/apache/superset/discussions/38439)
GitHub link: https://github.com/apache/superset/discussions/38439#discussioncomment-16006759
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] unable to setup using docker compose for 5.0.0 [superset]
Posted by "AFTABSHIAKH786 (via GitHub)" <gi...@apache.org>.
GitHub user AFTABSHIAKH786 added a comment to the discussion: unable to setup using docker compose for 5.0.0
Now I am getting this in network tab
<img width="1366" height="768" alt="image" src="https://github.com/user-attachments/assets/bce31c84-e330-4e0e-aaa7-feade1ac2a7d" />
GitHub link: https://github.com/apache/superset/discussions/38439#discussioncomment-16007830
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] unable to setup using docker compose for 5.0.0 [superset]
Posted by "dosubot[bot] (via GitHub)" <gi...@apache.org>.
GitHub user dosubot[bot] added a comment to the discussion: unable to setup using docker compose for 5.0.0
<!-- Answer -->
The 502 errors for static assets indicate [a race condition where nginx is trying to proxy requests to the webpack dev server, but the server isn't ready yet](https://github.com/apache/superset/pull/38161). This is a known issue - the `superset-node` container needs time to run `npm install` and start webpack, which [can take 10+ minutes](https://github.com/apache/superset/issues/31890#issuecomment-2644044130).
Check if the webpack dev server is running:
```bash
docker compose logs superset-node
```
Look for a message like `"webpack 5.x.x compiled successfully"`. If you don't see that yet, the build is still in progress.
Also, I notice you're accessing `http://localhost/superset/welcome/` - are you using a custom nginx configuration or reverse proxy? The default Docker dev setup serves on port 9000 directly (`http://localhost:9000`). If you have nginx in front, make sure it's configured to wait for the webpack server to be healthy before starting, or simply wait until the build completes.
If waiting doesn't help, try restarting just the node container after the other services are up:
```bash
docker compose restart superset-node
```
<!-- Dosu Comment Footer -->
*To reply, just mention [@dosu](https://go.dosu.dev/dosubot).*
---
<sup>How did I do? [Good](https://app.dosu.dev/response-feedback/0178b0c1-f6e2-4c63-ab4a-3e8e27154305?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/0178b0c1-f6e2-4c63-ab4a-3e8e27154305?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/0178b0c1-f6e2-4c63-ab4a-3e8e27154305?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/0178b0c1-f6e2-4c63-ab4a-3e8e27154305?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/0178b0c1-f6e2-4c63-ab4a-3e8e27154305?feedback_type=hallucination) | [Report š](https://app.dosu.dev/response-feedback/0178b0c1-f6e2-4c63-ab4a-3e8e27154305?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/0178b0c1-f6e2-4c63-ab4a-3e8e27154305?feedback_type=other)</sup>
[](https://app.dosu.dev/a28d3c7e-a9d3-459e-9fb6-3a6f9ff4f357/ask?utm_source=github) [](https://cursor.com/link/prompt?text=The%20502%20errors%20for%20static%20assets%20indicate%20%5Ba%20race%20condition%20where%20nginx%20is%20trying%20to%20proxy%20requests%20to%20the%20webpack%20dev%20server%2C%20but%20the%20server%20isn%27t%20ready%20yet%5D%28https%3A//github.com/apache/superset/pull/38161%29.%20This%20is%20a%20known%20issue%20-%20the%20%60superset-node%60%20container%20needs%20time%20to%20run%20%60npm%20install%60%20and%20start%20webpack%2C%20which%20%5Bcan%20take%2010%2B%20minutes%5D%28https%3A//github.com/apache/superset/issues/31890%23issuecomment-2644044130%29.%0A%0ACheck%20if%20the%20webpack%20dev%20server%20is%20running%3A%0A%60%60%60bash%0Adocker%20compose%20logs%20superset-node%0A%60%60%60%0A%0ALook%20for%20a%20message%20like%20%60%22webpack%205.x.x%20compiled%2
0successfully%22%60.%20If%20you%20don%27t%20see%20that%20yet%2C%20the%20build%20is%20still%20in%20progress.%0A%0AAlso%2C%20I%20notice%20you%27re%20accessing%20%60http%3A//localhost/superset/welcome/%60%20-%20are%20you%20using%20a%20custom%20nginx%20configuration%20or%20reverse%20proxy%3F%20The%20default%20Docker%20dev%20setup%20serves%20on%20port%209000%20directly%20%28%60http%3A//localhost%3A9000%60%29.%20If%20you%20have%20nginx%20in%20front%2C%20make%20sure%20it%27s%20configured%20to%20wait%20for%20the%20webpack%20server%20to%20be%20healthy%20before%20starting%2C%20or%20simply%20wait%20until%20the%20build%20completes.%0A%0AIf%20waiting%20doesn%27t%20help%2C%20try%20restarting%20just%20the%20node%20container%20after%20the%20other%20services%20are%20up%3A%0A%60%60%60bash%0Adocker%20compose%20restart%20superset-node%0A%60%60%60) [](https://go.dosu.dev/discord-bot) [](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/apache/superset/discussions/38439)
GitHub link: https://github.com/apache/superset/discussions/38439#discussioncomment-16007910
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org