User Request
Type: bug
Target: Console Application
Submitted by: @aashu2006
Console Request ID: 2652ac39-2fc2-49c0-975d-cf6bd2bc3dfb
Description
What happened:
In entrypoint.sh:1 and 27, the script declares #!/bin/sh but uses wait -n $BACKEND_PID $WATCHDOG_PID 2>/dev/null || wait $BACKEND_PID. wait -n is a bash extension not in POSIX sh. On Alpine-based Docker images where /bin/sh is busybox or ash, wait -n is unrecognised and 2>/dev/null silently swallows the error, falling through to || wait $BACKEND_PID and breaking the intended "exit when either process dies" behavior.
What I expected:
Either change the shebang to #!/bin/bash or rewrite the wait logic using POSIX-compatible constructs.
Steps to reproduce:
- Run entrypoint.sh in an Alpine container where /bin/sh is busybox
- Observe incorrect shutdown behavior when either process dies
This issue was automatically created from the KubeStellar Console.
User Request
Type: bug
Target: Console Application
Submitted by: @aashu2006
Console Request ID: 2652ac39-2fc2-49c0-975d-cf6bd2bc3dfb
Description
What happened:
In
entrypoint.sh:1and27, the script declares#!/bin/shbut useswait -n $BACKEND_PID $WATCHDOG_PID 2>/dev/null || wait $BACKEND_PID.wait -nis a bash extension not in POSIX sh. On Alpine-based Docker images where/bin/shis busybox or ash,wait -nis unrecognised and2>/dev/nullsilently swallows the error, falling through to|| wait $BACKEND_PIDand breaking the intended "exit when either process dies" behavior.What I expected:
Either change the shebang to
#!/bin/bashor rewrite the wait logic using POSIX-compatible constructs.Steps to reproduce:
This issue was automatically created from the KubeStellar Console.