Configure Docker log drivers and options in Application advanced settings

What problem will this feature address?

When deploying as an Application in Dokploy, it is not possible to define a Docker log driver like gelf and its options (e.g. gelf-address, tag) from the UI. This prevents setups that send logs directly to ELK (Elasticsearch, Kibana & Logstash) via the Docker logging driver, for example:

logging:
driver: gelf
options:
gelf-address: "udp://elk:12201"
tag: ldap

Where I have an ldap which I want to send the logs to the elk.

Describe the solution you'd like

In the Application “Advanced” settings, add:

• A field to choose the Docker logging.driver (e.g. gelf).
• A simple key/value editor for logging.options (e.g. gelf-address, tag).

Or even better a space to write the logging needed like this:
logging:
driver: gelf
options:
gelf-address: "udp://elk-node:12201"
tag: ldap

This would let an Application replicate the same logging configuration that currently only works via Docker Compose/Stack.

Describe alternatives you've considered

• Using a Docker Compose/Stack project in Dokploy so the logging: block is respected.
• Setting a global log-driver and log-opts in the Docker daemon, which forces the same logging config for every container on the host.

Additional context

No response

Will you send a PR to implement it?

No

No files, tests, or entry points are named. Start by locating the Application Advanced settings and the application deployment path, then trace how Compose/Stack logging is represented. Done means an Application can set logging.driver and logging.options and the resulting container uses them, with coverage for the settings.