Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Collapse
Brand Logo

Rig Community

  1. Home
  2. Feature ideas
  3. Container-interior process visibility (Docker / DDEV)

Container-interior process visibility (Docker / DDEV)

Scheduled Pinned Locked Moved Feature ideas
dockerddevcontainers
2 Posts 1 Posters 6 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • RigR Offline
    RigR Offline
    Rig
    Rig Team
    wrote last edited by
    #1

    Ask: Give Rig optional visibility into processes inside containers — not only host processes and published ports.

    Today: Rig is host-oriented. It can run Compose / DDEV as an outer process and see published localhost ports. It does not give deep visibility of processes inside containers the way / DDEV’s own tooling does.

    Why: Magento + DDEV (and other Docker-first) users need per-service status, interior PIDs/ports, and container logs without replacing Docker/DDEV as the runtime.

    Sketch:

    • Optional container-aware board for Compose / DDEV projects
    • Per-service status + logs via Docker CLI
    • MCP: surface container services under / without a raw shell

    Source: Prospect feedback (Magento 2 / DDEV), 2026-09-03. Tracked in .

    1 Reply Last reply
    1
    • RigR Offline
      RigR Offline
      Rig
      Rig Team
      wrote last edited by
      #2

      Canonical write-up (opening post may have mangled markdown from an earlier push):

      Ask: Give Rig optional visibility into processes inside containers — not only host processes and published ports.

      Today: Rig is host-oriented. It can run Compose / DDEV as an outer process and see published localhost ports. It does not give deep visibility of processes inside containers the way docker top / DDEV’s own tooling does.

      Why: Magento + DDEV (and other Docker-first) users need per-service status, interior PIDs/ports, and container logs without replacing Docker/DDEV as the runtime.

      Sketch:

      • Optional container-aware board for Compose / DDEV projects
      • Per-service status + logs via Docker CLI
      • MCP: surface container services under get_status / get_logs without a raw shell

      Source: Prospect feedback (Magento 2 / DDEV), 2026-09-03. Tracked in docs/feature-ideas-todo-2.md.

      1 Reply Last reply
      0

      Hello! It looks like you're interested in this conversation, but you don't have an account yet.

      Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

      With your input, this post could be even better 💗

      Register Login
      Reply
      • Reply as topic
      Log in to reply
      • Oldest to Newest
      • Newest to Oldest
      • Most Votes


      • Login

      • Don't have an account? Register

      • Login or register to search.
      • First post
        Last post
      0
      • Categories
      • Recent
      • Tags
      • Popular
      • World
      • Users
      • Groups