purple-plastic-57801
07/26/2023, 2:11 AMFROM balenalib/raspberrypi4-64-python:3.9-bullseye as deps
COPY ./dist/teletom.tom.entry/manager_deps.pex /binary-deps.pex
RUN PEX_TOOLS=1 python3 /binary-deps.pex venv --scope=deps --compile /bin/app
FROM balenalib/raspberrypi4-64-python:3.9-bullseye as srcs
COPY ./dist/teletom.tom.entry/manager_srcs.pex /binary-srcs.pex
RUN PEX_TOOLS=1 python3 /binary-srcs.pex venv --scope=srcs --compile /bin/app
FROM balenalib/raspberrypi4-64-debian:bullseye
...
COPY --from=deps /bin/app /bin/app
COPY --from=srcs /bin/app /bin/app
ENTRYPOINT ["/bin/app/pex"]
I'm seeing this issue
exec /bin/app/pex: no such file or directory
The file certainly exists!
My question is, if pants docker_image target does anything special to command or entrypoint? I certainly don't believe so..purple-plastic-57801
07/26/2023, 2:13 AMpurple-plastic-57801
07/26/2023, 2:14 AMroot@881d71296eed:/# /bin/app/pex
bash: /bin/app/pex: /bin/app/bin/python3.9: bad interpreter: No such file or directory
I recognize that this is how pex works.
If I set PEX_PYTHON_PATH it doesn't override itbitter-ability-32190
07/26/2023, 2:22 AMpurple-plastic-57801
07/26/2023, 2:22 AMpurple-plastic-57801
07/26/2023, 2:26 AMenough-analyst-54434
07/26/2023, 2:54 AMenough-analyst-54434
07/26/2023, 2:54 AM/bin/app/bin/python
(or one of the python* there) is a symlink to the original python3 in the different base image. No dice.enough-analyst-54434
07/26/2023, 2:55 AMenough-analyst-54434
07/26/2023, 3:01 AM