ModuleNotFoundError: No module named 'authlib' when implementing Google OAuth with Apache Superset Docker

[Ikarashi0310]

I'm encountering a ModuleNotFoundError: No module named 'authlib' error while hosting Apache Superset and attempting to implement Google authentication (OAuth). I'm blocked by this persistent error and cannot proceed.

I have attempted to explicitly install authlib in my custom Dockerfile.

Error Log

Traceback (most recent call last):
  File "/app/superset/app.py", line 40, in create_app
    app_initializer.init_app()
  File "/app/superset/initialization/__init__.py", line 489, in init_app
    self.init_app_in_ctx()
  File "/app/superset/initialization/__init__.py", line 413, in init_app_in_ctx
    self.configure_fab()
  File "/app/superset/utils/decorators.py", line 266, in wrapped
    return on_error(ex)
  File "/app/superset/utils/decorators.py", line 236, in on_error
    raise ex
  File "/app/superset/utils/decorators.py", line 259, in wrapped
    result = func(*args, **kwargs)
  File "/app/superset/initialization/__init__.py", line 566, in configure_fab
    appbuilder.init_app(self.superset_app, db.session)
  File "/usr/local/lib/python3.10/site-packages/flask_appbuilder/base.py", line 211, in init_app
    self.sm = self.security_manager_class(self)
  File "/usr/local/lib/python3.10/site-packages/flask_appbuilder/security/sqla/manager.py", line 62, in __init__
    super(SecurityManager, self).__init__(appbuilder)
  File "/usr/local/lib/python3.10/site-packages/flask_appbuilder/security/manager.py", line 278, in __init__
    from authlib.integrations.flask_client import OAuth
ModuleNotFoundError: No module named 'authlib'
Traceback (most recent call last):
  File "/usr/local/bin/superset", line 7, in <module>
    sys.exit(superset())
  File "/usr/local/lib/python3.10/site-packages/click/core.py", line 1157, in __call__
    return self.main(*args, **kwargs)
... (rest of the log, similar ModuleNotFoundError)
ModuleNotFoundError: No module named 'authlib'

Dockerfile

FROM apache/superset:latest

USER root
RUN apt update && apt install -y \
    python3-dev \
    default-libmysqlclient-dev \
    build-essential \
    pkg-config \
    && rm -rf /var/lib/apt/lists/*

RUN uv pip install --no-cache-dir mysqlclient pymysql gunicorn authlib==1.2.0

COPY superset_config.py /app/superset_home/superset_config.py
RUN chown superset:superset /app/superset_home/superset_config.py

USER superset

CMD ["gunicorn", "-w", "2", "--threads", "8", "-b", "0.0.0.0:8088", "superset.app:create_app()"]

Question
Even though I explicitly run uv pip install ... authlib==1.2.0 as the root user, the application is failing to import authlib when running as the superset user, resulting in a ModuleNotFoundError.

Why is the authlib package not being found, and how can I correctly install this dependency within the Superset image for OAuth to work?

Potential Hint / Context
I noticed in the official Superset documentation that dependencies are sometimes suggested to be added to a docker/requirements-local.txt file and rebuilt via docker-compose. However, I am trying to build a custom image using a standalone Dockerfile.

Could the issue be related to:

The uv pip install command placing the package in a location not accessible or recognized by the superset user/environment?

The apache/superset:latest base image using a Python virtual environment that isn't being targeted by the uv pip install command?

Any guidance on the correct way to layer dependencies onto the apache/superset base image to enable Google OAuth is greatly appreciated! 🙏

[dosubot[bot]]

The issue is that Superset runs inside a Python virtual environment located at /app/.venv, and installing packages with uv pip install or pip install as root may not always target the correct environment used at runtime. To ensure authlib is available, install it using either uv pip install authlib or /app/.venv/bin/pip install authlib in your Dockerfile before switching to the superset user. This guarantees the package is installed in the environment Superset uses when running as superset reference reference.

Here’s a recommended Dockerfile snippet:

FROM apache/superset:latest

USER root
RUN apt update && apt install -y \
    python3-dev \
    default-libmysqlclient-dev \
    build-essential \
    pkg-config \
    && rm -rf /var/lib/apt/lists/*

RUN uv pip install --no-cache-dir mysqlclient pymysql gunicorn authlib==1.2.0

USER superset

CMD ["gunicorn", "-w", "2", "--threads", "8", "-b", "0.0.0.0:8088", "superset.app:create_app()"]

If you still see the error, try replacing the uv pip install ... line with:

RUN /app/.venv/bin/pip install authlib==1.2.0

This directly targets the virtual environment Superset uses reference.

For older Superset images (pre-v5), uv may not be available, so use /app/.venv/bin/pip install <package> instead reference.

Alternatively, you can add dependencies to a requirements-local.txt file and rebuild your image via docker-compose, but for a standalone Dockerfile, the above approach is recommended reference.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}    

[Ikarashi0310]

@dosu
I'm still encountering a ModuleNotFoundError: No module named 'authlib' error even after editing the Dockerfile as shown below to install the packages directly into the Python virtual environment. Do you know a solution for this issue?

USER root
RUN apt update && apt install -y

python3-dev

default-libmysqlclient-dev

build-essential

pkg-config

python3-venv

&& rm -rf /var/lib/apt/lists/*

RUN python3 -m venv /app/.venv

RUN uv pip install --no-cache-dir mysqlclient pymysql gunicorn
RUN /app/.venv/bin/pip install authlib==1.2.0

COPY superset_config.py /app/superset_home/superset_config.py
RUN chown superset:superset /app/superset_home/superset_config.py

USER superset

CMD ["gunicorn", "-w", "2", "--threads", "8", "-b", "0.0.0.0:8088", "superset.app:create_app()"]

[dosubot[bot]]

The root cause is that recreating /app/.venv in your Dockerfile (with python3 -m venv /app/.venv) overwrites the pre-configured virtual environment from the Superset base image, removing all required packages and breaking Superset’s dependencies. This leads to persistent ModuleNotFoundError errors for packages like authlib and others reference reference.

Solution:
Do not recreate /app/.venv. Instead, install extra Python packages directly into the existing environment. Here’s the correct pattern:

FROM apache/superset:latest

USER root
RUN apt update && apt install -y \
    python3-dev \
    default-libmysqlclient-dev \
    build-essential \
    pkg-config \
    && rm -rf /var/lib/apt/lists/*

RUN uv pip install --no-cache-dir mysqlclient pymysql gunicorn authlib==1.2.0

COPY superset_config.py /app/superset_home/superset_config.py
RUN chown superset:superset /app/superset_home/superset_config.py

USER superset

CMD ["gunicorn", "-w", "2", "--threads", "8", "-b", "0.0.0.0:8088", "superset.app:create_app()"]

If uv isn’t available, use /app/.venv/bin/pip install <package> instead. You can verify the install during build with /app/.venv/bin/python -c "import authlib" reference.

For maintainability, you can add dependencies to a requirements-local.txt and install with uv pip install -r requirements-local.txt reference.

Let me know if you still see the error after removing the python3 -m venv /app/.venv line!

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}    

[Ikarashi0310]

@dosu
I've created the following Dockerfile and requirements-local.txt, but I'm still encountering the same error: ModuleNotFoundError: No module named 'authlib'.

dockerfile
↓

FROM apache/superset:latest

USER root
RUN apt update && apt install -y \
    python3-dev \
    default-libmysqlclient-dev \
    build-essential \
    pkg-config \
    && rm -rf /var/lib/apt/lists/*

COPY requirements-local.txt /app/requirements-local.txt
RUN uv pip install --no-cache-dir -r requirements-local.txt

COPY superset_config.py /app/superset_home/superset_config.py
RUN chown superset:superset /app/superset_home/superset_config.py

USER superset

CMD ["gunicorn", "-w", "2", "--threads", "8", "-b", "0.0.0.0:8088", "superset.app:create_app()"]

requirements-local.txt
↓

mysqlclient
pymysql
gunicorn
authlib==1.2.0

[dosubot[bot]]

The issue is that Superset’s Docker image expects requirements-local.txt to be placed in the docker/ directory (i.e., docker/requirements-local.txt), not /app/requirements-local.txt. The official bootstrap script only looks for the file in docker/ and installs it at container startup, not during the Docker build. Installing at build time or from a different path can result in packages not being available in the runtime environment, which causes the ModuleNotFoundError you’re seeing reference.

To fix this, move your requirements-local.txt into the docker/ directory of your build context (so it becomes docker/requirements-local.txt), and do not install it manually in the Dockerfile. The bootstrap script will automatically install these dependencies into the correct virtual environment when the container starts reference.

You do not need to add a RUN uv pip install ... line for requirements-local.txt in your Dockerfile. Just copy your requirements-local.txt to docker/ and rebuild your image. If you want to verify the install, you can add a test like RUN /app/.venv/bin/python -c "import authlib" after the install step.

This workflow matches the official pattern and should resolve the ModuleNotFoundError for authlib and any other Python dependencies reference.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}