Is that a right way that use docker entrypoint to excute .sh file and put process /sbin/init into the CMD ?

Hi, it's me again, I have a question about process /sbin/init in docker,
here is my dockerfile :
Dockfile
and my script.sh file:
script.sh
and my docker-compose.yml:
docker-compose.yml

base on these file I build a image and named "base", and excecute cmd docker-compose up and the log information like this :

you see the output log information stuck the message "Finished Update UTMP about System Runlevel Changes.", whereas I can still use ssh to visit the container , and so far everything is fine inside the container :

I worry about the situation that systemd log information stuck , here is my question:

1. Is there something wrong I don't know? if exist please tell me.
2. Is a right way that use docker entrypoint to excute script and put process /sbin/init into the CMD ?

thanks,
Xiaotong.Zhao

Start by reviewing the linked Dockerfile, script.sh, and docker-compose.yaml, then reproduce the docker-compose up output around “Finished Update UTMP about System Runlevel Changes.” Compare the entrypoint and CMD behavior with the container’s SSH access and /sbin/init process. Done means determining whether the stalled log indicates a problem or expected behavior and documenting the cause.