为什么使用.SH脚本作为入口点时，为什么Docker无法运行正确的CMD？

Question

我对Docker的新手（至少要比其他人构建的图像还要多），并且我陷入了这一模型。我正在使用Deno构建一个应用程序，并试图在Docker中运行它。我的基本形象是官员使用Alpine 的Deno图像，它使用.SH作为入口点。官方图像中定义的输入点脚本应该查看CMD中的第一个参数（在这种情况下为“运行”），如果它在列表中（它是），请使用DENO命令运行。相反，我有一个错误。

CMD

CMD run --allow-net --allow-read --lock=lock.json mod.ts

错误

/bin/sh: run: not found

当我在DENO中进行硬码时，

运行良好。 cmd deno run - allow-net - allow-read-lock = lock.json mod.ts

我不知道为什么它不通过脚本作为入口点来工作。我在做什么错？

docker-entry.sh

#!/bin/sh
set -e

if [ "$1" != "${1#-}" ]; then
    # if the first argument is an option like `--help` or `-h`
    exec deno "$@"
fi

case "$1" in
    bundle | cache | compile | completions | coverage | doc | eval | fmt | help | info | install | lint | lsp | repl | run | test | types | uninstall | upgrade | vendor )
    # if the first argument is a known deno command
    exec deno "$@";;
esac

exec "$@"

我的dockerfile

FROM denoland/deno:alpine-1.19.2

# The port that your application listens to.
EXPOSE MYPORTNUMBER

WORKDIR /app

# Prefer not to run as root.
USER deno

# Cache the dependencies as a layer (the following two steps are re-run only when deps.ts is modified).
# Ideally cache deps.ts will download and compile _all_ external files used in main.ts.
COPY deps.ts .
RUN deno cache deps.ts

# These steps will be re-run upon each file change in your working directory:
ADD . .
# Compile the main app so that it doesn't need to be compiled each startup/entry.
RUN deno cache mod.ts

CMD run --allow-net --allow-read --lock=lock.json mod.ts

基本图像信息在这里