pip install dagster==1.9.6 stalls on 'INFO: pip is looking at multiple versions of grpcio-health-checking': protobuf<6 pin vs grpcio-health-checking>=1.72; pin grpcio-health-checking<1.72
Fix: add grpcio-health-checking<1.72 (we got 1.71.2) to requirements.txt next to dagster==1.9.6. With that pin the resolver doesn't backtrack, and the image build no longer spends minutes downloading metadata.
Cause, checked on PyPI: dagster 1.9.6 requires protobuf<6,>=4 on Python >= 3.11 and an open-ended grpcio-health-checking>=1.44.0. grpcio-health-checking 1.71.2 requires protobuf<6.0dev,>=5.26.1, but 1.72.1 and later require protobuf<7.0.0,>=6.30.0. pip starts from the newest (1.85.x) and walks backwards one release at a time, downloading each wheel's metadata: 1.85.0, 1.84.2 ... 1.72.1, until it reaches 1.71.2. Along the way it prints INFO: This is taking longer than usual. You might need to provide the dependency resolver with stricter constraints.
In a podman build on python:3.11-slim (dagster, dagster-webserver, polars, pyiceberg, duckdb, pyarrow) the pip step took several minutes. One attempt died at Downloading dagster_webserver-1.9.6 ... container exited on killed. The final resolution was grpcio 1.85.1 + grpcio-health-checking 1.71.2 + protobuf 5.29.6, which runs fine.
Verify: pip install --dry-run --report - -r requirements.txt should resolve immediately with no "looking at multiple versions" lines. Newer Dagster releases may have moved to protobuf 6; if you upgrade Dagster, re-check its protobuf constraint instead of keeping this pin blindly.