fix: print error when docker build fails

[typed-sigterm]

What is this PR about?

We keep getting errors like:

Initializing deployment
Build static
Pulling registry.dev.paperchemis.com/paper_chemis/backend:latest: ✅
WARNING! Using --password via the CLI is insecure. Use --password-stdin.
Login Succeeded
latest: Pulling from paper_chemis/backend
Digest: sha256:2120ec5911d210f2addc380e1f1e2838cee59ace83750ad0918bc3da2069f9ea
Status: Image is up to date for registry.dev.paperchemis.com/paper_chemis/backend:latest
registry.dev.paperchemis.com/paper_chemis/backend:latest
❌ Error

No one knows what the problem is...

Checklist

Before submitting this PR, please make sure that:

• You created a dedicated branch based on the canary branch.
• You have read the suggestions in the CONTRIBUTING.md file https://github.com/Dokploy/dokploy/blob/canary/CONTRIBUTING.md#pull-request
• You have tested this PR in your local instance.

[Siumauricio]

Instead of this we should do something like, because error can be an object

Suggested change

	writeStream.write("❌ ${error}");
	writeStream.write("❌ ${error instanceof Error ? error.message : "Unknown error"}");

[typed-sigterm]

But `${new Error('message')}` is evaluated to Error: message without losing information

[Siumauricio]

In any case, that code does nothing; it will only print ${error} as a string.

[typed-sigterm]

😮😅

[Siumauricio]

In any case, that code does nothing; it will only print ${error} as a string.