how-to · machine Open this in the console

Restart or stop a Docker app.

Network › containers. The name is the Coolify or Compose app. The buttons are there while the machine is connected.

There is no shell inside the container. Restart, stop, and start are the actions. Logs is the recent lines. Each power action is audited.
01

Open Network › containers

While the machine is connected, a running app has logs, restart, and stop. A stopped app has start instead of restart and stop, and it still has logs. accounts-web, accounts-db, redis, and traefik are running. old-web is exited, so that row says start. Logs asks the agent for recent lines. Restart and stop ask you to confirm, then send that action. There is no shell inside the container. The machine in this picture is painted connected so the buttons are visible. It still has no tunnel, so logs and a confirm here would not reach Docker.

Containers tab with logs, restart, and stop on each running app
Accounts server, connected. Each running app has logs, restart, and stop. Nothing has been pressed.
02

Press restart, then confirm

Press restart on accounts-web. The label becomes confirm restart?. Press it again to send restart to the agent. This shot stops on the confirm, so the app is not restarted. Stop is the same two presses — Stop a Docker app. Start is the button on old-web, the app that is not running — Start a stopped Docker app. The second press is audited. Selecting the app so a later unhealthy state emails someone is See Docker apps on a machine.

Containers tab with restart on accounts-web changed to confirm restart
Restart on accounts-web is asking to confirm. The second press has not happened.

Recent lines are Read a Docker app's logs. Stop, on its own, is Stop a Docker app. Start on an app that is not running is Start a stopped Docker app. Seeing the list, and selecting an app so an unhealthy one becomes an alert, is See Docker apps on a machine. A named check, with an interval and healthy or running, is Check that a Docker app is running.