fix: resolved database startup script not checking docker daemon status @0pilatos0

[0pilatos0]

Closes #1974

✅ Checklist

• I have followed every step in the contributing guide (updated 2022-10-06).
• The PR title follows the convention we established conventional-commit
• I performed a functional test on my final commit

---

Changelog

added an extra check in the initial steps of the start-database.sh script to check if the docker daemon is up and running to prevent the script from continuing with for example generating the password

---

Examples

before:

❯ ./start-database.sh
Cannot connect to the Docker daemon at unix:///Users/paulvanderlei/.docker/run/docker.sock. Is the docker daemon running?
Cannot connect to the Docker daemon at unix:///Users/paulvanderlei/.docker/run/docker.sock. Is the docker daemon running?
You are using the default database password
Should we generate a random password for you? [y/N]:

after:

❯ ./start-database.sh
Docker deamon is not up and running. Please start docker and try again.

💯

[changeset-bot]

🦋 Changeset detected

Latest commit: 7a87f46

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
create-t3-app	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
create-t3-app	✅ Ready (Inspect)	Visit Preview	💬 1 unresolved ✅ 1 resolved	Aug 31, 2024 9:54am

[vercel]

@0pilatos0 is attempting to deploy a commit to the t3-oss Team on Vercel.

A member of the Team first needs to authorize it.