bug: bentoml containerize failed by uv installation location change

[lingw777]

Describe the bug

My CICD build is failing at bentoml containerize

RUN curl -LO https://astral.sh/uv/install.sh &&     sh install.sh && rm install.sh && mv $HOME/.cargo/bin/uv /usr/local/bin/
#12 0.858 downloading uv 0.5.0 x86_64-unknown-linux-gnu
#12 1.514 installing to /root/.local/bin
#12 1.553 mv: cannot stat '/root/.cargo/bin/uv': No such file or directory

It's probably related to recent uv release. See astral-sh/uv#8913

To reproduce

No response

Expected behavior

No response

Environment

bentoml: 1.3.10
python: 3.10
platform: --opt platform=linux/amd64,linux/arm64

[lingw777]

Found this breaking change in uv release note

Use XDG (i.e. ~/.local/bin) instead of the Cargo home directory in the installer (#8420)

Previously, uv's installer used $CARGO_HOME or ~/.cargo/bin for its target install directory. It's been a longstanding complaint that uv uses this directory, as there's no relationship to Cargo. Now, uv will be installed into $XDG_BIN_HOME, $XDG_DATA_HOME/../bin, or ~/.local/bin (in that order). Note that $UV_INSTALL_DIR can always be used to override the target directory. Upgrading with uv self update will not move uv to the new install directory.

and bentoML base docker image scripts pull from latest installation scripts https://astral.sh/uv/install.sh but still trying to mv $HOME/.cargo/bin/uv
See

BentoML/src/bentoml/_internal/container/frontend/dockerfile/templates/base_debian.j2

Line 17 in 0088c75

sh install.sh && rm install.sh && mv $HOME/.cargo/bin/uv /usr/local/bin/

[frostming]

The fix is on the way to the next release.

[mobecks]

Workaround until next release (worked for me):
change above-mentioned "line 17" to
sh install.sh && rm install.sh && mv $HOME/.local/bin/uv /usr/local/bin/