dosubot[bot]
commented
2 months ago I found some similar issues and discussions that might help you resolve the 404 Not Found errors for static assets in Superset when using Docker:
-
Closed Issue: GET /ws HTTP/1.1 werkzeug.exceptions.NotFound: 404 Not Found
- This issue was resolved by ensuring that the static assets are correctly built and copied into the final Docker image [1].
-
Closed Issue: NotFound errors on 2.0.1rc2
- The suggested solution was to move to
docker-composeand ensure proper setup and configuration [2].
- The suggested solution was to move to
-
Closed Issue: [Errno 99] Cannot assign requested address in superset_init for docker-compose
- A non-dev Docker compose file was added to help with frontend assets [3].
To resolve the 404 Not Found errors for static assets, follow these steps:
-
Verify the build process: Ensure that the
npm run buildcommand completes without errors and generates the necessary static assets. -
Check the asset paths: Ensure that the paths to the static assets are correct and that they are being copied to the expected location in the final Docker image.
-
Run the Docker build without skipping the build step: Make sure
DEV_MODEis set tofalseto ensure the assets are built and copied:docker build --build-arg DEV_MODE=false -t your-superset-image . -
Configure Nginx correctly: Ensure that your Nginx configuration is set up to serve the static assets properly. Here is a sample configuration snippet from
docker/nginx/nginx.conf:server { listen 80 default_server; server_name _; location /ws { proxy_pass http://superset_websocket; proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "Upgrade"; proxy_set_header Host $host; } location / { proxy_pass http://superset_app; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $remote_addr; proxy_set_header X-Forwarded-Host $host; proxy_set_header X-Forwarded-Proto $scheme; proxy_http_version 1.1; port_in_redirect off; proxy_connect_timeout 300; } }
Additionally, ensure that you follow the steps outlined in the Superset Docker documentation for proper setup and configuration:
-
Prerequisites:
- Install Docker
- Install Docker Compose
-
Configuration:
- The
/app/pythonpathfolder is mounted from./docker/pythonpath_devwhich contains a base configuration./docker/pythonpath_dev/superset_config.pyintended for use with local development. - For local overrides, copy
./docker/pythonpath_dev/superset_config_local.exampleto./docker/pythonpath_dev/superset_config_docker.pyand fill in your overrides.
- The
-
Initializing Database:
- The database will initialize itself upon startup via the init container (
superset-init). This may take a minute.
- The database will initialize itself upon startup via the init container (
-
Normal Operation:
- To run the container, simply run:
docker compose up - After waiting several minutes for Superset initialization to finish, you can open a browser and view
http://localhost:8088.
- To run the container, simply run:
By following these steps, you should be able to resolve the 404 Not Found errors for static assets in Superset when using Docker [4][5][6].
To continue talking to Dosu, mention @dosu.
pesekon2
Darrenzzy
mistercrunch
fuomag9
Bug description
website img
docker log -f
How to reproduce the bug
Screenshots/recordings
No response
Superset version
master / latest-dev
Python version
3.9
Node version
16
Browser
Chrome
Additional context
No response
Checklist