fix: Added a condition, if docker is alive or not. #1983

[Sapython]

This caused problems when docker was not running which resulted in the CLI misinforming me that the database was already running. But it wasn't.

Closes #

✅ 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

[Short description of what has changed]
Added a simple condition to run docker info to check if the docker daemon is actually running or not.

Screenshots

[Screenshots]

In this image you can see that the both of the execution of start-database.sh are successful. But the second one should fail because I killed the docker daemon but the CLI wasn't able to pick it up.
💯

[changeset-bot]

⚠️ No Changeset found

Latest commit: 4c0b925

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a 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	Sep 19, 2024 2:57pm

[vercel]

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

A member of the Team first needs to authorize it.