Building lightly modified openvidu-call lead to entrypoint not found

I’ve produced a lightly modified version of openvidu-call (only visual changes to existing components) - I had it running in a development environment without incident, but I’m currently attempting to deploy it - having built using the dockerfile.node provided, I replaced the openvidu-call image in the docker-compose.override.yml, however the container is failing to start, stating /usr/local/bin/ exec: line 11: /usr/local/bin/ not found - I’ve reviewed and the entrypoint script is present in the source and valid, and no error is reported by the docker build at that stage, with logs approximately looking as follows

Step 13/15 : COPY docker/ /usr/local/bin/
 ---> 7f0917f9bab6
Step 14/15 : RUN apk add curl &&     chmod +x /usr/local/bin/
 ---> Running in bcdf6558dd3b
(1/5) Installing ca-certificates (20220614-r0)
(2/5) Installing brotli-libs (1.0.9-r6)
(3/5) Installing nghttp2-libs (1.47.0-r0)
(4/5) Installing libcurl (7.83.1-r4)
(5/5) Installing curl (7.83.1-r4)
Executing busybox-1.35.0-r17.trigger
Executing ca-certificates-20220614-r0.trigger
OK: 10 MiB in 21 packages
Removing intermediate container bcdf6558dd3b
 ---> eb5700903829
Step 15/15 : CMD ["/usr/local/bin/"]
 ---> Running in 3c072b138b7d
Removing intermediate container 3c072b138b7d
 ---> ae4af59571c6
Successfully built ae4af59571c6

Anyone have experience as to what could be causing this, or whether I’m missing something obvious? Happy to provide more information if needed.

From what directory are you running the build command?

/root/openvidu-call/ - containing folders docker, openvidu-call-back, openvidu-call-back-java & openvidu-call-front - the command being run follows:

root@<hostname>:~/openvidu-call# docker build -f docker/Dockerfile.node -t test --no-cache .

Apologies for bumping, but I’ve yet to find any resolution and am hoping to get more people to see it.

Hello @NeonCoding sorry for the late response. Is there any possibility to check the source code? Just to see on my machine what may be happening.


The error was caused because of characters /r/n present at the

Not related with OpenVidu, all files are ok in Openvidu Call repository.