ModuleNotFoundError: No module named 'superset'

[kalyan540]

Hi,
Iam facing this issue with the latest superset installation.
Command executed 'docker compose up'
Any Suggessions towards resolve this issue would be greatful. @dosu

System info :
ubuntu 24

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

[dosubot[bot]]

To resolve the "ModuleNotFoundError: No module named 'superset'" error when running docker compose up on Ubuntu 24, ensure that you have cloned the Superset repository correctly and are using the appropriate Docker Compose file. Here are the steps you should follow:

1. Clone the Superset Repository:
   Make sure you have cloned the Superset repository using the following command:

   git clone --depth=1 https://github.com/apache/superset.git

2. Use the Correct Docker Compose Command:
   Depending on your use case, you should use one of the following commands to start Superset:

   • For an interactive development environment:

     docker compose up --build

   • For building a set of immutable images from the local branch:

     docker compose -f docker-compose-non-dev.yml up

   • For booting up an official release:

     export TAG=3.1.1
     docker compose -f docker-compose-image-tag.yml up

3. Verify Dockerfile Configuration:
   Ensure that your Dockerfile is correctly set up to install Superset and its dependencies. The Dockerfile should include steps to install necessary packages and set up the environment, as shown in the provided Dockerfile.from_local_tarball. Key steps include:

   • Installing necessary system dependencies like build-essential, libssl-dev, and libffi-dev.
   • Installing Node.js and npm for building the frontend.
   • Using pip to install Python dependencies from requirements/base.txt.

Ensure that you are in the correct directory where the docker-compose.yml or the respective Docker Compose file is located before running these commands. If the error persists, verify that Docker and Docker Compose are installed and configured correctly on your system. Additionally, ensure that the environment variables and paths are correctly set in your Dockerfile to include Superset in the PYTHONPATH ^[1][2].

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other}

[kalyan540]

@dosu,
fatal: unable to access , git clone --depth=1 https://github.com/apache/superset.git

[dosubot[bot]]

The "fatal: unable to access" error usually indicates a network issue or a problem with accessing the repository. Here are some steps to troubleshoot and resolve this:

1. Check Internet Connection:
   Ensure that your internet connection is stable and working properly.

2. Verify URL:
   Double-check the URL you are using to clone the repository. It should be:

   git clone --depth=1 https://github.com/apache/superset.git

3. Network Restrictions:
   If you are behind a firewall or using a VPN, ensure that it allows access to GitHub. You might need to adjust your network settings or contact your network administrator.

4. Try a Different Network:
   If possible, try cloning the repository from a different network to rule out local network issues.

5. Use SSH Instead:
   If HTTPS is blocked, try using SSH to clone the repository:

   git clone --depth=1 [email protected]:apache/superset.git

   Ensure you have SSH keys set up with your GitHub account.

6. Check GitHub Status:
   Occasionally, GitHub services might be down. Check the GitHub status page to ensure there are no ongoing issues.

If these steps do not resolve the issue, please provide more details about any error messages you receive during the cloning process.

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other}

[kalyan540]

@dosu
Still the same issue, "ModuleNotFoundError: No module named 'superset'"

[alberk8]

I am also new here. I am trying to build from the 4.1.1 release and it is still cranking away for the last 10minutes.

[alberk8]

Even the release 4.1.1 is not working. Same error.

[kalyan540]

i found this while iam surfing through discusssions.

#31281 (comment)

[alberk8]

I spoke too soon and managed to get it to work by running the superset-init which created the login user, This is based on 4.1.1 source code.

Steps

1. Download the source tar.gz and extract to a directory.
2. docker compose build and this took something on my old PC.
3. docker compose up -d
4. Open browser, http://192.168.1.10
5. cannot login as it complain about invalid login
6. docker compose up superset-init
7. Open Browser again, now can login.

OS hosting Superset is Ubuntu 24.04 and docker V24.4.0

[kalyan540]

@alberk8, It worked ! Thanks for the solution

I opened another terminal, docker compose up superset-init exected this command solves the issue.

This is an issue with the new commits, don't know exact problem (maybe failure of superset_init), but we have to mention to developers.

[samraHanif0340]

The following solution worked for me 31281