Incomplete UI

[newtester805]

Hello
I have tried the production docker-compose installation, but when logged on the browser, the UI is not shown correctly. Assets such as the icon and the style of the page is not available. I have tested on both Google Chrome and Firefox browsers.

How to reproduce the bug

1. Follow the instructions at: https://superset.apache.org/docs/installation/installing-superset-using-docker-compose to install superset
2. Go to the browser and set: localhost:8088
3. See the page similar to the one attach here

Expected results

I was expecting to see something similar to: https://git.cloudron.io/cloudron/superset-app/-/blob/main/screenshots/apache_superset_00.jpg?ref_type=heads

Actual results

See attached screenshot.

Screenshots

If applicable, add screenshots to help explain your problem.

Environment

• browser type and version: Google Chrome Version 117.0.5938.132 (Official Build) (64-bit)
• superset version: 2.0
• python version: Python 3.9.18
• node.js version: node -v

The app container does not seen to have npm installed. It gives a "Command not found" error when executing:

$docker exec -it <app container> /bin/bash
#node -v
node: Command not found

[sfirke]

You say you are using Superset 2.0.0, how are you specifying that to Docker? Can you confirm that when you click Settings, in the bottom of the dropdown bar it says 2.0.0 and not 0.0.0-dev?

[mathenymi]

I am having the same issue with python3.10 on Superset 3.0.0

[mookie-]

The problem is due to the content-security-policy header.

This is the error message:

Content-Security-Policy: The page’s settings blocked the loading of a resource at inline (“style-src”).

I'm not very experienced with CSP, so I don't know but perhaps it has to do with this commit: 1716b9f

[sfirke]

cc @dpgaspar , who wrote that pull request -- any thoughts?

[newtester805]

You say you are using Superset 2.0.0, how are you specifying that to Docker? Can you confirm that when you click Settings, in the bottom of the dropdown bar it says 2.0.0 and not 0.0.0-dev?

You are correct, it says 0.0.0-dev

[SaviorXTanren]

I can also confirm this issue reproduced in 3.0.0 with a Content Security Policy error in the console when attempting to use a remotely hosted image for the app icon. Just upgraded from 2.1.0 to 3.0.0 today and this was working fine previously on 2.1.0.

[sfirke]

I believe this has been closed by #25468. Please reply if that is not the case.

[newtester805]

I can confirm that for 3.0.0 it is now fixed, not using the docker-compose without tag.