A very fun problem I ran into while starting my docker containers.
How does someone execute a second command after running a first command that hasn't completed or maybe it is a never exiting process like running a server?
&& is the typical solution that comes in mind but scripts don't work that way and they rely on return values from previous commands.
& is something that can be very useful because it runs commands in the background.
I was stuck because I couldn't just exit the script ad it would kill the container.
So after hours of searching ways to trigger the functionality I finally had a big brain moment and here's the magic code that did the job.