pipenv lock fails with RenovateBot: ResolutionError

[oatnog]

When I pipenv upgrade my_dependency==1.2.3 then pipenv lock on my own machine, using Python 3.12.10 and various versions of Pipenv (including 2024.4.1 and 2025.0.1), it works. It works locally.

But when it's run with the Renovate Bot https://github.com/renovatebot/renovate, I see this "ResolutionFailure" error.

Any thoughts on what I can do to resolve this issue? I assume it's an environment thing, but I've tried to make sure the version of Python and of Pyenv are exactly the same.

Command failed: pipenv lock
Locking  dependencies...
ERROR:pip.subprocessor:Getting requirements to build wheel exited with 1
[ResolutionFailure]:   File 
"/opt/containerbase/tools/pipenv/2025.0.1/3.12.10/lib/python3.12/site-packages/p
ipenv/resolver.py", line 451, in main
[ResolutionFailure]:       _main(
[ResolutionFailure]:   File 
"/opt/containerbase/tools/pipenv/2025.0.1/3.12.10/lib/python3.12/site-packages/p
ipenv/resolver.py", line 436, in _main
[ResolutionFailure]:       resolve_packages(
[ResolutionFailure]:   File 
"/opt/containerbase/tools/pipenv/2025.0.1/3.12.10/lib/python3.12/site-packages/p
ipenv/resolver.py", line 400, in resolve_packages
[ResolutionFailure]:       results, resolver = resolve_deps(
[ResolutionFailure]:       ^^^^^^^^^^^^^
[ResolutionFailure]:   File 
"/opt/containerbase/tools/pipenv/2025.0.1/3.12.10/lib/python3.12/site-packages/p
ipenv/utils/resolver.py", line 979, in resolve_deps
[ResolutionFailure]:       results, hashes, internal_resolver = 
actually_resolve_deps(
[ResolutionFailure]:       ^^^^^^^^^^^^^^^^^^^^^^
[ResolutionFailure]:   File 
"/opt/containerbase/tools/pipenv/2025.0.1/3.12.10/lib/python3.12/site-packages/p
ipenv/utils/resolver.py", line 747, in actually_resolve_deps
[ResolutionFailure]:       resolver.resolve()
[ResolutionFailure]:   File 
"/opt/containerbase/tools/pipenv/2025.0.1/3.12.10/lib/python3.12/site-packages/p
ipenv/utils/resolver.py", line 474, in resolve
[ResolutionFailure]:       raise ResolutionFailure(message=e)
Your dependencies could not be resolved. You likely have a mismatch in your 
sub-dependencies.
You can use $ pipenv run pip install <requirement_name> to bypass this 
mechanism, then run $ pipenv graph to inspect the versions actually installed in
the virtualenv.
Hint: try $ pipenv lock --pre if it is a pre-release dependency.
ERROR: Getting requirements to build wheel exited with 1

Your dependencies could not be resolved. You likely have a mismatch in your 
sub-dependencies.
You can use $ pipenv run pip install <requirement_name> to bypass this 
mechanism, then run $ pipenv graph to inspect the versions actually installed in
the virtualenv.
Hint: try $ pipenv lock --pre if it is a pre-release dependency.
ERROR: Failed to lock Pipfile.lock!

[oatnog]

I have an idea. My deps include gdal = "==3.6.2", which are bindings to a C++ library. That library is installed on my local machine, but not on renovate docker image. Could that be the source of the sub-dependency ResolutionFailure?
I specifically exclude this dependency from renovate's list of packages to check for updates. But maybe Pipenv is still unable to calculate the deps correctly if its lockfile assumes I have the GDAL wheel or its dependencies?

[oatnog]

I solved this by making sure the renovate cron jobs run on an image with the C library dependency installed. Instead of using the renovate image directly, I build and image with this simple wrapper:

FROM docker.io/renovate/renovate:latest
USER root
RUN apt-get update && apt-get install -y \
    libgdal-dev \
    gdal-bin \
    && rm -rf /var/lib/apt/lists/*
USER ubuntu

And configure renovate to run on that instead. Pipenv then works as expected.