From Docker Compose

The flow

1. Add service → From Compose.
2. Paste or upload your docker-compose.yml.
3. Pier inspects the file and:
   • Injects pier-net as the default network (replacing any network_mode: bridge or unnamed network).
   • Strips host-port bindings (ports: sections). Traffic reaches containers through Traefik only.
   • Allocates internal ports for each service that exposes one.
4. Click Deploy.

Pier runs docker compose up in its own working directory and streams the logs to the UI in real time.

What this means for your Compose file

You write Compose as if for a developer laptop. Pier handles the production wiring:

• No ports: mappings — remove them or let Pier strip them; everything is on pier-net.
• No external networks — Pier will override them. If you truly need a second network, ask on GitHub.
• No volume conflicts — each stack gets prefixed volume names.

Compose stack vs multi-service project

A Compose stack is one service in Pier — you redeploy the whole stack at once. If you want to deploy and scale services independently, create them as separate Pier services and connect them via pier-net DNS names.