private python pypi repo not working with dagger.

[severe river]

I am encountering an issue while using a private Python package in a Dagger pipeline. The package is hosted on a private PyPI repository, and the error occurs when calling a Dagger method that uses this package.

In pyproject.toml, I have defined an [uv.tools.pip] section with extra-index-url pointing to our private PyPI repository:

[uv.tools.pip]
extra-index-url = "https://<private-repo-url>"

When I execute the Dagger pipeline, I see the following error:

× No solution found when resolving dependencies:
╰─▶ Because Library was not found in the package registry and your
project depends on Library, we can conclude that your
project's requirements are unsatisfiable.

I have verified that,

1. The private PyPI repository is accessible from my machine.
2. The package installs correctly using uv pip install.
3. The pyproject.toml file includes the correct extra-index-url.

dagger version - v0.13.6

[near anvil]

👋 not sure if this is currently supported. cc @slender iris

[slender iris]

Dagger modules don't use the uv pip interface, they use the project management features of uv.lock. So what you're looking for is here: https://docs.astral.sh/uv/configuration/indexes/

[[tool.uv.index]]
url = "https://<private-repo-url>"

[near anvil]

Thx Helder. How about private packages? does Dagger honor the UV username and pass env variables?

[slender iris]

The engine doesn't propagate anything UV specific, do you know if it mounts netrc?

I don't see netrc being mentioned in any PR or in code. \cc @scarlet sigil

@rocky torrent, you've worked only with private Dagger modules support, right? Not private language packages?

[near anvil]

it doesn't 😦

[rocky torrent]

You're right ; we do not mount the netrc, it is something that could be added via the client session config file issue that Justin proposed