Dokploy / Dokploy/dokploy

View all containers (remote servers via ssh + swarm) in a single page

Open
#1,696 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
TypeScript
Stars
37.4k
Forks
3k
Avg merge
1d 3h
Merged PRs (30d)
73

Description

What problem will this feature address?

I have created a docker swarm cluster for dokploy and then added a SSH key and connection to my usual docker raspberry pi server but I am unable to view all of the containers in a single place.

Today, as of v0.21.6 you do not see the containers listed under Docker page

Image

For SSH servers, the information is hidden from view and not listed. To view which containers are running on my non-swarm node I must:

  • Go to Remote Servers
  • Click 3 dots, under menu > Extra I must click Show Docker Containers

Then this shows up:

Image

Why isn't this information all aggregated and listed on the main menu Docker section?

Describe the solution you'd like

I would like to be able to view, in a single page, all my docker containers that dokploy has visibility into which should include Remote Servers (SSH) as well as the swarm. All of them should be listed under Docker page and of course there should be a marker to indicate which one is running on standalone docker vs. docker-swarm managed by dokploy.

Describe alternatives you've considered

The workaround are the nasty steps I listed which has me clicking multiple pages and sections of the website and it does not show me a comprehensive view of the infrastructure, I must check every server individually to see whats running there. .

Portainer can show me everything it can see or manage, so I guess that's a workaround if I did not want to use Dokploy (which I do want to use, hence this bug)

Additional context

No response

Will you send a PR to implement it?

No

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the main Docker page and compare it with Remote Servers > Extra > Show Docker Containers for SSH servers and the existing swarm view. Trace how each view obtains and labels containers; done means one Docker page lists containers from visible SSH servers and the swarm, with a marker distinguishing standalone Docker from Docker Swarm.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, typescript
Domain
devops, frontend, infrastructure
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.