Repository navigation
RuntimeError: Could not find libc2pa_c.so in any of the search paths (Platform: x86_64-unknown-linux-gnu, Architecture: x86_64) #187
Description
Hi
I'm encountering a persistent runtime error when using c2pa-python==0.27.1 inside an AWS Fargate (x86_64) container.
Despite documentation and changelogs stating that Linux x86_64 support was added in recent releases, the package still fails to locate the bundled libc2pa_c.so library.
RuntimeError: Could not find libc2pa_c.so in any of the search paths
(Platform: x86_64-unknown-linux-gnu, Architecture: x86_64)
This happens consistently on AWS Fargate, even though:
The image runs python:3.10-bullseye (Debian, glibc)
The architecture is confirmed as x86_64
The container installs c2pa-python==0.27.1 directly from PyPI
Environment:
Python: 3.10
c2pa-python: 0.27.1
Base image: python:3.10-bullseye
Platform: AWS Fargate (Linux, x86_64)
OS/Arch inside container: Linux x86_64 GNU
Deployment method: Docker + ECS task definition (runtime_platform.cpu_architecture = X86_64)
dockerfile
FROM python:3.10-bullseye
RUN apt-get update && apt-get install -y --no-install-recommends
libgl1
libglib2.0-0
libopenblas-dev
liblapack-dev
libjpeg-dev
zlib1g-dev
curl
unzip
&& rm -rf /var/lib/apt/lists/*
WORKDIR /app
COPY requirements.txt .
RUN pip install --upgrade pip setuptools wheel
RUN pip install --no-cache-dir "c2pa-python"
RUN pip install --no-cache-dir -r requirements.txt
COPY app/ ./app/
Activity
tmathern commentedon Oct 23, 2025
I think the error reported is misleading (I'll fix that in a follow-up PR).
The native library needs GLIBC 2.32. Looking at the version you use in your Docker, it has 2.31. So a later version will work.
For instance, I used the following Docker to debug, and c2pa-python loaded there:
Can you update to a newer version?
mimideannointed-star commentedon Oct 23, 2025
Thank you i am no longer getting that error :)
tmathern commentedon Oct 24, 2025
The library loading fix also got merged, it will be part of next release.