To Reproduce

1. Create a new database (MongoDB or Redis) deployment and configure it.
2. Go to advanced tab and set resource limits.
3. Click Deploy.

Current vs. Expected behavior

Current Behaviour

The set resource limits are not respected. This can be confirmed both from the application's "Monitoring" tab and directly running the docker command in the server.

Expected Behaviour

The set resource limits must be respected. Not having this can be extremely fatal to the server where a database service, under abnormal circumstances, can take up the entire CPU or / and Memory available in the server and lead to a machine freeze.

Provide environment information

Dokploy Version: v0.28.4
Provider: AWS / Hetzner (happening on both)
Application type: Database (I've faced this on MongoDB and Redis specifically, but could be widespread).

Which area(s) are affected? (Select all that apply)

Databases

Are you deploying the applications where Dokploy is installed or on a remote server?

Same server where Dokploy is installed

Additional context

No response

Will you send a PR to fix it?

Maybe, need help