[P0] Single-container lifecycle: start_container / stop_container / restart_container #1

Closed
opened 2026-05-18 12:26:43 +02:00 by marcus · 0 comments
Owner

Gap

The connector only offers project-level start/stop/redeploy. There is no way to start, stop, or restart an individual container within a multi-container project.

Container Manager equivalent

The Container tab allows starting, stopping, and restarting individual containers.

Suggested approach

Add start_container, stop_container, restart_container to modules/containers.py. DSM API: SYNO.Docker.Containerstop is already confirmed working (used during live testing). start and restart are very likely analogous methods, name JSON-encoded.

Reverse-engineering effort

Low — stop confirmed; start/restart need quick verification.

Priority

P0 — high value for debugging multi-container projects without restarting the whole project.

## Gap The connector only offers project-level start/stop/redeploy. There is no way to start, stop, or restart an individual container within a multi-container project. ## Container Manager equivalent The Container tab allows starting, stopping, and restarting individual containers. ## Suggested approach Add `start_container`, `stop_container`, `restart_container` to `modules/containers.py`. DSM API: `SYNO.Docker.Container` — `stop` is already confirmed working (used during live testing). `start` and `restart` are very likely analogous methods, `name` JSON-encoded. ## Reverse-engineering effort Low — `stop` confirmed; `start`/`restart` need quick verification. ## Priority P0 — high value for debugging multi-container projects without restarting the whole project.
Sign in to join this conversation.
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: marcus/mcp-synology-container#1