latest Containerfile on master no longer builds: `failed to remove directory `/opt/app-root`: Resource busy (os error 16)`

[Fogapod]

$ podman build . -t docling_serve

STEP 1/16: FROM quay.io/sclorg/python-312-c9s:c9s
STEP 2/16: USER 0
--> Using cache 0edc28236dafe2bf949ed4e59634d6a7d2f476c1b7ecba96d81db9b144dd3d1b
--> 0edc28236daf
STEP 3/16: RUN --mount=type=bind,source=os-packages.txt,target=/tmp/os-packages.txt     dnf -y install --best --nodocs --setopt=install_weak_deps=False dnf-plugins-core &&     dnf config-manager --best --nodocs --setopt=install_weak_deps=False --save &&     dnf config-manager --enable crb &&     dnf -y update &&     dnf install -y $(cat /tmp/os-packages.txt) &&     dnf -y clean all &&     rm -rf /var/cache/dnf
--> Using cache 1e608d61a9027ae29204efd6b02012e15d4af8020973d737dd5d00d5ac1ea566
--> 1e608d61a902
STEP 4/16: RUN /usr/bin/fix-permissions /opt/app-root/src/.cache
--> Using cache 5413b6a59c329fe0fe1ce2d9e48d14a0f8a98406dc9bfa722f160082d496ce1f
--> 5413b6a59c32
STEP 5/16: ENV TESSDATA_PREFIX=/usr/share/tesseract/tessdata/
--> Using cache 7e63c13deadfcbc8809965d4159897a4ef03429ce6f9cc7e23ca021be13a9bba
--> 7e63c13deadf
STEP 6/16: USER 1001
--> Using cache f0d8bd6a4c5ad6fc6030a2c4b15ef850242581ea16db3ba3fd1f3c6308b9a498
--> f0d8bd6a4c5a
STEP 7/16: WORKDIR /opt/app-root/src
--> Using cache a3c3bf2c08d928e68650f0fe642ed7f3f1a8b23776be4e348d55f6a65da6251a
--> a3c3bf2c08d9
STEP 8/16: ENV     OMP_NUM_THREADS=4     LANG=en_US.UTF-8     LC_ALL=en_US.UTF-8     PYTHONIOENCODING=utf-8     UV_COMPILE_BYTECODE=1     UV_LINK_MODE=copy     UV_PROJECT_ENVIRONMENT=/opt/app-root     DOCLING_SERVE_ARTIFACTS_PATH=/opt/app-root/src/.cache/docling/models
--> Using cache f15d5a8f832ff99e8a43c93ee66f5e3514bccba21069afe8df12dfa46eaf54a7
--> f15d5a8f832f
STEP 9/16: ARG UV_SYNC_EXTRA_ARGS=""
--> Using cache 6d3dbf069235d546119487d365b1482fba8fa0db00be19c9ecc7f1955586e7f1
--> 6d3dbf069235
STEP 10/16: RUN --mount=from=ghcr.io/astral-sh/uv:0.7.13,source=/uv,target=/bin/uv     --mount=type=cache,target=/opt/app-root/src/.cache/uv,uid=1001     --mount=type=bind,source=uv.lock,target=uv.lock     --mount=type=bind,source=pyproject.toml,target=pyproject.toml     umask 002 &&     UV_SYNC_ARGS="--frozen --no-install-project --no-dev --all-extras" &&     uv sync ${UV_SYNC_ARGS} ${UV_SYNC_EXTRA_ARGS} --no-extra flash-attn &&     FLASH_ATTENTION_SKIP_CUDA_BUILD=TRUE uv sync ${UV_SYNC_ARGS} ${UV_SYNC_EXTRA_ARGS} --no-build-isolation-package=flash-attn
Using CPython 3.12.11 interpreter at: /usr/bin/python3.12
error: failed to remove directory `/opt/app-root`: Resource busy (os error 16)
Error: building at STEP "RUN --mount=from=ghcr.io/astral-sh/uv:0.7.13,source=/uv,target=/bin/uv --mount=type=cache,target=/opt/app-root/src/.cache/uv,uid=1001 --mount=type=bind,source=uv.lock,target=uv.lock --mount=type=bind,source=pyproject.toml,target=pyproject.toml umask 002 &&     UV_SYNC_ARGS="--frozen --no-install-project --no-dev --all-extras" &&     uv sync ${UV_SYNC_ARGS} ${UV_SYNC_EXTRA_ARGS} --no-extra flash-attn &&     FLASH_ATTENTION_SKIP_CUDA_BUILD=TRUE uv sync ${UV_SYNC_ARGS} ${UV_SYNC_EXTRA_ARGS} --no-build-isolation-package=flash-attn": while running runtime: exit status 2

Same error with docker and any combination of extras like --build-arg=UV_SYNC_EXTRA_ARGS='--no-group pypi --group cu124 --no-extra rapidocr --no-extra tesserocr'

[dosubot]

This build error appears to be related to how the uv tool (recently updated to 0.7.13) manages its project environment and interacts with the directory structure and mounts in the Containerfile. The error occurs during the uv sync step, with /opt/app-root set as UV_PROJECT_ENVIRONMENT and /opt/app-root/src as the working directory—a subdirectory of the project environment. There is no custom logic in the Containerfile or project scripts that explicitly removes or locks /opt/app-root; the issue likely comes from uv's internal logic or its interaction with the build setup, especially with the complex mounts and user context changes in the Dockerfile. This is not specific to Podman or Docker, nor to any particular combination of extras or build arguments, and there are no open issues or documentation in the repo addressing this "Resource busy" error.

You might try experimenting with setting UV_PROJECT_ENVIRONMENT to a different directory (not a parent of the working directory), or adjusting the working directory to avoid this overlap, as this could help avoid directory locking conflicts during the build. No known workarounds or best practices for this specific scenario are documented in the repo.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}   

[Fogapod]

Looks like this might be related: astral-sh/uv#14411
Fixed in astral-sh/uv#14404 in 0.7.19

I don't see a warning mentioned in fix but image builds now