Add documentation for intermediate Docker layers in a workspace

[zanieb]

No description provided.

[charliermarsh]

I think I would recommend --frozen here, isn't it much simpler? That's what we tend to do in our own Dockerfiles.

[zanieb]

In what sense? --frozen here doesn't change anything because the whole workspace has been added already, it'd be up above where using --frozen instead of --locked makes things simpler.

I don't think we should recommend --frozen in general though, because I think --locked asserting that your uv.lock is not stale is meaningful and helpful.

I think it's fine to recommend --frozen above and rely on this subsequent --locked to catch a stale lock, but I worry that will also be confusing to people (i.e., I recommended exactly this in the issue and the user opted to do the additional mounts instead)

[charliermarsh]

Sorry, I meant to comment on the line above. I personally find it unnecessary to enumerate all of the pyproject.toml files in the uv sync --no-install-workspace when you're doing a locked install here anyway? (But -- again personally -- I wouldn't use --locked in a Dockerfile, I think that validation should be done in CI.)

In pyx at least, we instead use --frozen for this install phase, but enumerate all the workspace members when we do the ADD (to minimize invalidation).

[zanieb]

Yeah... I'll change it.

[zhcn000000]

If I need to install all the packages for a specific workspace, how should I handle it? If I directly use uv sync --package, will the packages in the project root directory be ignored

[zanieb]

Yeah, use --package.

[codspeed-hq]

CodSpeed Performance Report

Merging #16787 will degrade performances by 19.45%

_{Comparing zb/docker-workspace (29fc564) with main (d6eb285)}

Summary

❌ 1 regression
✅ 5 untouched

⚠️ Please fix the performance issues or acknowledge them on CodSpeed.

Benchmarks breakdown

	Mode	Benchmark	BASE	HEAD	Change
❌	Simulation	resolve_warm_airflow	808.3 ms	1,003.6 ms	-19.45%