How to run superset with "docker compose up --build" command.

[andrewcaoo]

I am trying to run superset on my local laptop. I cloned superset's code from official reposity. After that, i ran: docker compose up --build. Everything ran smoothly untill the superset-init service run. It show that "No module named 'superset'". This is full message:

2024-12-04 14:32:06 Skipping local overrides
2024-12-04 14:32:06 Unknown Operation!!!
2024-12-04 14:32:07 
2024-12-04 14:32:07 ######################################################################
2024-12-04 14:32:07 
2024-12-04 14:32:07 
2024-12-04 14:32:07 Init Step 1/4 [Starting] -- Applying DB migrations
2024-12-04 14:32:07 
2024-12-04 14:32:07 
2024-12-04 14:32:07 ######################################################################
2024-12-04 14:32:07 
2024-12-04 14:32:07 Traceback (most recent call last):
2024-12-04 14:32:07   File "/usr/local/bin/superset", line 5, in <module>
2024-12-04 14:32:07     from superset.cli.main import superset
2024-12-04 14:32:07 ModuleNotFoundError: No module named 'superset'

Please help me, I can't find out what is superset module and how i can install them.

[dosubot[bot]]

Hey @andrewcaoo! I'm here to help you with any bugs, questions, or contributions you have regarding Superset. Let's tackle this issue together!

A similar issue was reported where the error "No module named 'trino'" occurred during the Docker Compose installation. The suggested solution was to specify version 3.0.1 and, if you had tried to install on the master branch, to clean up the Docker environment using the following commands:

docker container prune
docker volume prune
docker volume rm superset_db_home

This might help resolve the "No module named 'superset'" error as well ^[1].

Additionally, ensure that the Python environment in the Docker container is correctly set up. The Superset Dockerfile uses a Python base image and installs dependencies using a script. Make sure that the requirements/base.txt file is correctly referenced and that the Superset package is installed in editable mode ^[2].

If the issue persists, double-check the Dockerfile and the docker-compose.yml to ensure all paths and volumes are correctly configured.

To continue talking to Dosu, mention @dosu.

[UriSaShavit]

Same here :(

[andrewcaoo]

Same here :(

I ran "docker-compose-non-dev" instead. I don't what is difference. I still apply my change in the frontend, backend code.

[UriSaShavit]

I did it as well, didn't work (why should it? It depends on the same image). Tried also to reclone the repo

[UriSaShavit]

I found that the init script failws due to a missing mapping in the pythonpath. In the docker/.env line 49, I changed to: PYTHONPATH=/app:/app/pythonpath:/app/docker/pythonpath_dev

I don't want to commit to that, since I saw later on that the Werkzeug package throw errors, but it was sufficient enough for my POC with the tool

[samraHanif0340]

This worked for me as well
Thanks @UriSaShavit