Feature Request: Improve Docker Images Tab

What problem will this feature address?

Improve the Docker Images tab to provide more complete image management directly from the UI.

Describe the solution you'd like

1. Add a Pull Image Action for Each Image

Add a Pull button to the Actions column for each image, alongside the existing View and Remove actions.

For example:

Actions
[ View ] [ Pull ] [ Remove ]

The Pull action should use the image's existing repository and tag to run the equivalent of:

docker pull <repository>:<tag>

For example:

nginx:latest
redis:7
ghcr.io/example/app:v1.2.3

After a successful pull:

• Show a success notification.
• Refresh the image list.
• Update the image's metadata/status in the table.

2. Indicate When an Image Is Outdated

Show an Outdated indicator when a newer version of the image is available in its registry.

For example:

Repository                  Tag       Status
------------------------------------------------
nginx                       latest    Outdated
redis                       7         Outdated
postgres                    17

3. Add Rows per Page

Add a Rows per page selector to the image table pagination, to make it consistent with other pages like the dashboard/overview page

Suggested options:

10
25
50
100

Describe alternatives you've considered

The current workaround is to manually run docker pull <image> on the server through an SSH session or another Docker management tool. This works, but it requires leaving the Dokploy UI and manually determining the correct image repository and tag.

Another option would be to provide only a single global "Pull Image" button, but a per-image Pull action is more convenient because the image reference is already known from the selected row and avoids requiring the user to enter it again.

Additional context

No response

Will you send a PR to implement it?

Maybe, need help

Start by locating the Docker Images tab and comparing its table actions and pagination with the dashboard/overview page. Trace the existing image-management flow before deciding where pulling, registry freshness checks, notifications, refreshes, and status updates belong. Done means per-image Pull and Outdated behavior work reliably and the table offers 10, 25, 50, and 100 rows per page.