LiveKit 1.0.22: Failed to load dynlib/dll '/usr/bin/app/_internal/livekit/rtc/resources/liblivekit_ffi.so'

[jezell]

LiveKit 1.0.22 has broken our deploys

yimod03_ctypes.install.<locals>.PyInstallerImportError: Failed to load dynlib/dll '/usr/bin/app/_internal/livekit/rtc/resources/liblivekit_ffi.so'. Most likely this dynlib/dll was not found when the application was frozen.

App is building with pyinstaller:

RUN pyinstaller --hidden-import livekit.rtc.resources --collect-data livekit --collect-binaries livekit --onedir --distpath /out --name app \
        app/cli.py

Pinning livekit to 1.0.20 fixes the problem:

"livekit==1.0.20",

[davidzhao]

@jezell which OS are you installing this on? the binaries are in place as far as I can see.

[davidzhao]

if you could share the docker script (redact anything proprietary), that'd be helpful

[jezell]

@davidzhao here's a trimmed down multi stage build. meshagent-router in this case is the app being built, but the rest is publically available pypi stuff. Base image here is:

python:3.13-slim-trixie on linux/amd64

Dockerfile:

# syntax=docker/dockerfile:1.6
ARG PY_VER=3.13

ARG PY_VER=3.13
FROM python:${PY_VER}-slim-trixie AS os-base

# ---------------------------------------------------------------------------
# 1. TOOLCHAIN & VENV
# ---------------------------------------------------------------------------
RUN apt-get update && apt-get install -y --no-install-recommends git binutils && \
    rm -rf /var/lib/apt/lists/*


FROM os-base AS build-base
ENV VENV=/opt/venv
RUN python -m venv "$VENV"
ENV PATH="$VENV/bin:$PATH" PIP_NO_CACHE_DIR=1

# ---------------------------------------------------------------------------
# 1. TOOLCHAIN & VENV
# ---------------------------------------------------------------------------
RUN apt-get update && apt-get install -y --no-install-recommends git binutils && \
    rm -rf /var/lib/apt/lists/*
ENV VENV=/opt/venv
RUN python -m venv "$VENV"
ENV PATH="$VENV/bin:$PATH" PIP_NO_CACHE_DIR=1

WORKDIR /src

# ---------------------------------------------------------------------------
# 2. COPY EVERYTHING **ONCE** 
# ---------------------------------------------------------------------------
#   – all SDKs
COPY meshagent-sdk ./meshagent-sdk
#   – common libs (used by every service)
COPY meshagent-router   ./meshagent-router # app

# ---------------------------------------------------------------------------
# 3. SINGLE dependency install
# ---------------------------------------------------------------------------
RUN pip install uv
RUN uv pip install --upgrade pip pytest pyinstaller && \
    # SDKs
    uv pip install \
        "meshagent-sdk/meshagent-api[all]" \
        "meshagent-sdk/meshagent-agents[all]" \
        meshagent-sdk/meshagent-tools \
        meshagent-sdk/meshagent-openai \
        meshagent-sdk/meshagent-livekit \
        meshagent-sdk/meshagent-computers \
        meshagent-sdk/meshagent-otel

RUN uv pip install -e meshagent-router # app

# ---------------------------------------------------------------------------
# 4. SERVICE‑STAGES
# ---------------------------------------------------------------------------

FROM build-base AS build-router
WORKDIR /src
COPY --from=build-web  /src/meshagent-cloud/meshagent/cloud/web/dist /src/meshagent-cloud/meshagent/cloud/web/dist
RUN pyinstaller --collect-data meshagent.cloud --collect-data stripe --hidden-import livekit.rtc.resources --collect-data livekit --collect-binaries livekit  --paths /src/meshagent-sdk  --onedir --distpath /out --name meshagent-router \
        meshagent-router/meshagent/router/cli.py


FROM os-base AS runtime-router
COPY --from=mime /etc/mime.types /etc/mime.types
COPY --from=build-router  /out/meshagent-router    /usr/bin/meshagent-router 

ENTRYPOINT ["/usr/bin/meshagent-router/meshagent-router"]

[davidzhao]

thanks @jezell we see what's happening.. fixing it!

[cloudwebrtc]

Hey @jezell, I've created a new .so file that lazily loads these additional dependencies here https://github.com/livekit/rust-sdks/actions/runs/20291831356. Would you mind downloading the corresponding liblivekit_ffi.so and replacing it to test? I only kept the regular system dependencies in the new .so. Any feedback would be greatly appreciated.

[jezell]

@cloudwebrtc looks like github prevents artifact downloads for unauthenticated users, so it's a bit challenging to dynamically download the right arch from the run to test a build. If you could maybe get a prerelease of livekit up on pypi it would make it a little easier to verify the whole process with the updated .so before it's published.

[cloudwebrtc]

Oh, sorry about that, but we've released a new fix:
https://github.com/livekit/python-sdks/releases/tag/rtc-v1.0.23

[jezell]

@cloudwebrtc looks like it's still happening with livekit 1.0.23 release