Managing a docker compose stack from your phone comes down to four commands. docker compose ps shows status and docker compose logs -f --tail 100 service follows a log. docker compose restart service restarts a service and docker compose pull && docker compose up -d updates images. Run them all from the directory holding the compose file.

docker compose ps: checking service status from your phone

docker compose ps lists the project's containers with their name, service, status and published ports. It is the first command to run after connecting: it tells you whether something restarted, whether a service exited with an error or whether its healthcheck reports unhealthy. Run it in the directory containing the compose file, or name the project with -p.

cd /srv/app
docker compose ps
docker compose ps -a
docker compose ps --services
docker compose ps --format "table {{.Name}}\t{{.Status}}"

On a phone screen, the full table wraps across several lines. -a includes stopped containers, --services prints only service names, and --format keeps just the columns that fit in portrait.

docker compose logs -f --tail 100: following one service without flooding the screen

--tail 100 limits output to the last 100 lines per container, and -f keeps the log open, printing new lines as they arrive. Without a service name, Compose interleaves output from the whole project, which is unreadable on a phone, so always name the service.

docker compose logs -f --tail 100 api
docker compose logs --since 10m api
docker compose logs -t --tail 50 api worker
docker compose logs --tail 200 api | grep -i error
  • --since 10m shows only what happened in the last ten minutes.
  • -t adds a timestamp to every line.
  • | grep -i error filters the text before it reaches the screen.

Press Ctrl+C to stop following the log; the container keeps running. The system keyboard on iOS and Android has no Ctrl key. The termi1 keyboard adds it alongside Esc, Tab and the arrow keys, plus an fn layer with PgUp/PgDn, Home and End.

docker compose restart and pull && up -d: restarting and updating step by step

docker compose restart api restarts the service's containers without recreating them, so it does not pick up changes to the compose file, environment variables or image. For that you need docker compose up -d, which recreates only the containers whose configuration or image has changed.

docker compose restart api
docker compose pull && docker compose up -d
docker compose pull api && docker compose up -d api

A safe sequence for updating from your phone:

  1. Check status with docker compose ps before touching anything.
  2. Pull the images with docker compose pull; if it fails, nothing has stopped yet.
  3. Apply the changes with docker compose up -d, which recreates the affected containers and returns the prompt.
  4. Verify with docker compose ps again that everything is running.
  5. Watch the startup with docker compose logs -f --tail 100 api and leave with Ctrl+C.

Chaining with && ensures up -d only runs if pull finishes without an error.

docker compose on mobile versus desktop: comparison table

What is comparedDesktopiOS/Android with termi1
Stopping logs -f with Ctrl+CPhysical Ctrl keyCtrl key on the built-in keyboard
Esc, Tab and arrowsAlways availableOn the termi1 keyboard; the system keyboard hides them
Switching from wifi to mobile dataNetwork usually fixedMosh keeps the session open
Long pull with the phone lockedMachine stays ontmux keeps the process and its output
Checking compose.yaml or .envLocal editor or scpBuilt-in SFTP without leaving the session
Typing long commandsFull keyboardSuggestions while typing or AI that drafts the command

Mosh, tmux and termi1 AI for docker compose in production

Mosh uses UDP, on ports 60000-61000 by default, and starts mosh-server over an initial SSH connection, so those ports must be open on the server. With Mosh, a running docker compose logs -f survives leaving the office and switching to mobile data.

For long operations, run them inside tmux, the terminal multiplexer:

tmux new -s deploy
docker compose pull && docker compose up -d
# Ctrl+b then d to detach
tmux attach -t deploy

The AI in termi1, the mobile SSH terminal turns a phrase such as “follow the api logs” into the command and types it at the prompt without pressing Enter. In “Review” mode it never presses Enter. In “Safe auto” only a limited set of commands recognised as safe get it. On connections tagged as production, Production Guard blocks any automatic Enter and holds back anything that stops or changes something, such as a restart, before it reaches the prompt. The AI never opens the session or receives keys: the private key is generated and stored in the phone's secure storage.

If the server has no public IP, a private mesh network such as Prialo or Tailscale lets you reach it over SSH without opening ports. termi1 is free on the App Store for iPhone and on Google Play.

Frequently asked questions

How do I exit docker compose logs -f without stopping the container?

docker compose logs -f exits with Ctrl+C, which only stops following the log; the containers keep running. On a phone you need a keyboard with a Ctrl key, like the termi1 keyboard, or a client that offers one in an extra bar above the system keyboard.

What is the difference between docker compose restart and docker compose up -d?

docker compose restart restarts existing containers without recreating them, so it ignores changes to the image, environment variables or compose file. docker compose up -d compares the current configuration and recreates, in the background, only the containers that changed. After a pull, up -d is the right command.

Why does docker compose ps show no containers?

docker compose ps only lists containers for the project in the current directory and, without -a, it hides stopped ones. If you run it from another folder, cd into the compose file's directory, pass the file path with -f, or give the project name with -p.

Can I manage docker compose from my phone without opening port 22?

Docker compose can be managed from a phone without exposing TCP port 22 to the internet by using a private mesh network such as Prialo or Tailscale. The phone and server reach each other inside that network, and the SSH or Mosh connection travels through it without public ports.