We've recently upgraded to `flytekit >= 1.13.5`...
# flyte-support
a
We've recently upgraded to
flytekit >= 1.13.5
and are seeing errors while pointing to our private remote pypi server? It seems like the switch to
uv
is a breaking change for us(this issue describes our problem of trying to rely on the standard pip config - https://github.com/astral-sh/uv/issues/1404). When we try to use
ImageSpec
now we get errors like:
Copy code
ERROR: failed to solve: process "/bin/sh -c /usr/bin/uv     pip install --python /opt/micromamba/envs/runtime/bin/python --index-url <https://pypi.python.org/simple/--extra-index-url> https://{PRIVATE_REPOSITORY_URL}/pypi/pycommon-store/simple/     --requirement requirements_uv.txt" did not complete successfully: exit code: 2
I'm assuming others are using private pypi servers? Do we need to shift away from the standard pip config to uv specific config now?
f
Are you injecting a
pip.conf
into the ImageSpec builder?
If you want to use the old ImageSpec behavior (with pip), you can install
pip install flytekitplugins-envd
and set
ImageSpec(builder="envd")
a
Ok, we can do the builder work around
f
Thank you! I'll take a look at it.