Windows 10 Docker - 找不到入口点

Question

On my work there is a docker project with all backend setup. The code of dockerfile:

FROM python:3.9.6-alpine

# Установка локальных переменных
ENV PYTHONDONTWRITEBYTECODE 1
ENV PYTHONUNBUFFERED 1

RUN mkdir -p /usr/src/freedom
WORKDIR /usr/src/freedom

# Установка зависимостей для Django
RUN apk update \
    && apk add postgresql \
    && apk add postgresql-dev \
    && apk add gcc libc-dev make git libffi-dev openssl-dev python3-dev libxml2-dev libxslt-dev \
    && apk add jpeg-dev zlib-dev libjpeg libffi-dev
#     && pip install Pillow \
#     && apk del build-deps

# ENV LANG C.UTF-8
# ENV LC_ALL C.UTF-8

CMD python3 --version
CMD . env/bin/activate
COPY ./requirements.txt ./requirements.txt

RUN pip install --upgrade pip
RUN pip install -r requirements.txt

COPY . .

# run entrypoint.sh
ENTRYPOINT ["/usr/src/freedom/entrypoint.sh"]

When running the project with docker-compose up --build (right after clonning, no shenanigans) on Linux everything works fine. It finds its entrypoint.sh fine) its okay. When running from windows entrypoint dont run.

• Running entrypoint from a global path like "C:/abc/abc/.."

Please help

I tried:

• Removing ENTRYPOINT and running it as CMD
• Adding entry point to /usr/src/freedom on my C: folder
• Changing paths

Answer 1

One option you have is to call the shell and execute the file, as if: ENTRYPOINT ["/bin/sh", "-c", "sh /usr/src/freedom/entrypoint.sh"]

But in the end I think the best solution will be to simply use a single CMD instruction, like: CMD ["/usr/src/freedom/entrypoint.sh"] (with this I mean you should remove all the CMD and ENTRYPOINT instructions you currently have and use this one.)

You can check the difference between CMD and ENTRYPOINT in the documentation and this SoF post:

• https://docs.docker.com/engine/reference/builder/#understand-how-cmd-and-entrypoint-interact
• What is the difference between CMD and ENTRYPOINT in a Dockerfile?

Also, as stated in the documentation, having two CMD commands is useless since the latest one is the one that will be applied.

Answer 2

The error "entrypoint not found" in Windows 10 when using Docker typically indicates that the specified entrypoint script or executable cannot be found in the container. This can occur for a few reasons:

The entrypoint script or executable is not present in the image or container.

The entrypoint script or executable is not located in the correct directory.

The entrypoint script or executable is not set to be executable.

The script name is misspelled.

There might be some compatibility issue with the image and the version of windows

To resolve this issue, you can try to:

Check that the entrypoint script or executable is present in the container and is located in the correct directory.
Ensure that the script or executable is set to be executable.
Verify the name of the script and make sure it is spelled correctly.
Try to run the image on different version of windows or try with different image.
If nothing works, you can try to rebuild the image, including the entrypoint script or executable.