Set execute permissions for startup scripts

[zhuomuniao1986]

Add execute permissions to start_vernemq and join_cluster scripts

Otherwise, the following error will be reported at startup

docker: Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: exec: "start_vernemq": executable file not found in $PATH

[ioolkos]

@zhuomuniao1986 Thanks, it seems this was never necessary before, though. Anything special in your environment?

---

👉 Thank you for supporting VerneMQ: https://github.com/sponsors/vernemq
👉 Using the binary VerneMQ packages commercially (.deb/.rpm/Docker) requires a paid subscription

[zhuomuniao1986]

There are no special.

I tested it again, and the issue can be reproduced. The image can be created successfully, but an error occurs when starting the container.

ubuntu@VM-16-15-ubuntu:/zmn/vernemq-test$ docker run \
>   -e "DOCKER_VERNEMQ_ALLOW_ANONYMOUS=on" \
>   -e "DOCKER_VERNEMQ_ACCEPT_EULA=yes" \
>   --name zmn2_vernemq \
>   -p 1883:1883 \
>   -p 8080:8080 \
>   -p 8888:8888 \
>   -d zmn2/vernemq:2.1.1
7fe9d8c0c87e3104648d691066e4d97cbca45bec46369d72e78153563e1e862e
docker: Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: exec: "start_vernemq": executable file not found in $PATHn

Run 'docker run --help' for more information

Test environment: Operating System — Ubuntu 24.04 LTS, Docker version 28.5.1

Please see the attached log for details and help check whether there’s anything wrong with my operation.

2025-10-28_11-11-02.log