​
Podman

Run the TraseAI gateway in a rootless Podman container. Uses the same image as Docker (build from the repo Dockerfile).

​
Requirements

  • Podman (rootless)
  • Sudo for one-time setup (create user, build image)

​
Quick start

1. One-time setup (from repo root; creates user, builds image, installs launch script): 
./setup-podman.sh
This also creates a minimal ~traseai/.mk-rcp/traseai.json (sets gateway.mode="local") so the gateway can start without running the wizard. By default the container is not installed as a systemd service, you start it manually (see below). For a production-style setup with auto-start and restarts, install it as a systemd Quadlet user service instead: 
./setup-podman.sh --quadlet
(Or set TRASEAI_PODMAN_QUADLET=1; use --container to install only the container and launch script.) 2. Start gateway (manual, for quick smoke testing): 
./scripts/run-traseai-podman.sh launch
3. Onboarding wizard (e.g. to add channels or providers): 
./scripts/run-traseai-podman.sh launch setup
Then open http://127.0.0.1:18789/ and use the token from ~traseai/.traseai/.env (or the value printed by setup).

​
Systemd (Quadlet, optional)

If you ran ./setup-podman.sh --quadlet (or TRASEAI_PODMAN_QUADLET=1), a Podman Quadlet unit is installed so the gateway runs as a systemd user service for the traseai user. The service is enabled and started at the end of setup.
  • Start: sudo systemctl --machine traseai@ --user start traseai.service
  • Stop: sudo systemctl --machine traseai@ --user stop traseai.service
  • Status: sudo systemctl --machine traseai@ --user status traseai.service
  • Logs: sudo journalctl --machine traseai@ --user -u traseai.service -f
The quadlet file lives at ~traseai/.config/containers/systemd/traseai.container. To change ports or env, edit that file (or the .env it sources), then sudo systemctl --machine traseai@ --user daemon-reload and restart the service. On boot, the service starts automatically if lingering is enabled for traseai (setup does this when loginctl is available). To add quadlet after an initial setup that did not use it, re-run: ./setup-podman.sh --quadlet.

​
The traseai user (non-login)

setup-podman.sh creates a dedicated system user traseai:
  • Shell: nologin — no interactive login; reduces attack surface.
  • Home: e.g. /home/traseai — holds ~/.traseai (config, workspace) and the launch script run-traseai-podman.sh.
  • Rootless Podman: The user must have a subuid and subgid range. Many distros assign these automatically when the user is created. If setup prints a warning, add lines to /etc/subuid and /etc/subgid: 
    traseai:100000:65536
    Then start the gateway as that user (e.g. from cron or systemd): 
    sudo -u traseai /home/traseai/run-traseai-podman.sh
sudo -u traseai /home/traseai/run-traseai-podman.sh setup
  • Config: Only traseai and root can access /home/traseai/.traseai. To edit config: use the Control UI once the gateway is running, or sudo -u traseai $EDITOR /home/traseai/.mk-rcp/traseai.json.

​
Environment and config

  • Token: Stored in ~traseai/.traseai/.env as TRASEAI_GATEWAY_TOKEN. setup-podman.sh and run-traseai-podman.sh generate it if missing (uses openssl, python3, or od).
  • Optional: In that .env you can set provider keys (e.g. GROQ_API_KEY, OLLAMA_API_KEY) and other TraseAI env vars.
  • Host ports: By default the script maps 18789 (gateway) and 18790 (bridge). Override the host port mapping with TRASEAI_PODMAN_GATEWAY_HOST_PORT and TRASEAI_PODMAN_BRIDGE_HOST_PORT when launching.
  • Paths: Host config and workspace default to ~traseai/.traseai and ~traseai/.traseai/workspace. Override the host paths used by the launch script with TRASEAI_CONFIG_DIR and TRASEAI_WORKSPACE_DIR.

​
Useful commands

  • Logs: With quadlet: sudo journalctl --machine traseai@ --user -u traseai.service -f. With script: sudo -u traseai podman logs -f traseai
  • Stop: With quadlet: sudo systemctl --machine traseai@ --user stop traseai.service. With script: sudo -u traseai podman stop traseai
  • Start again: With quadlet: sudo systemctl --machine traseai@ --user start traseai.service. With script: re-run the launch script or podman start traseai
  • Remove container: sudo -u traseai podman rm -f traseai — config and workspace on the host are kept

​
Troubleshooting

  • Permission denied (EACCES) on config or auth-profiles: The container defaults to --userns=keep-id and runs as the same uid/gid as the host user running the script. Ensure your host TRASEAI_CONFIG_DIR and TRASEAI_WORKSPACE_DIR are owned by that user.
  • Gateway start blocked (missing gateway.mode=local): Ensure ~traseai/.mk-rcp/traseai.json exists and sets gateway.mode="local". setup-podman.sh creates this file if missing.
  • Rootless Podman fails for user traseai: Check /etc/subuid and /etc/subgid contain a line for traseai (e.g. traseai:100000:65536). Add it if missing and restart.
  • Container name in use: The launch script uses podman run --replace, so the existing container is replaced when you start again. To clean up manually: podman rm -f traseai.
  • Script not found when running as traseai: Ensure setup-podman.sh was run so that run-traseai-podman.sh is copied to traseai’s home (e.g. /home/traseai/run-traseai-podman.sh).
  • Quadlet service not found or fails to start: Run sudo systemctl --machine traseai@ --user daemon-reload after editing the .container file. Quadlet requires cgroups v2: podman info --format '{{.Host.CgroupsVersion}}' should show 2.

​
Optional: run as your own user

To run the gateway as your normal user (no dedicated traseai user): build the image, create ~/.traseai/.env with TRASEAI_GATEWAY_TOKEN, and run the container with --userns=keep-id and mounts to your ~/.traseai. The launch script is designed for the traseai-user flow; for a single-user setup you can instead run the podman run command from the script manually, pointing config and workspace to your home. Recommended for most users: use setup-podman.sh and run as the traseai user so config and process are isolated.