Skip to main content

​
Podman

Run the Fased 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 ~fased/.fased/fased.json (sets gateway.mode="local") so the gateway can start without interactive onboarding. By default the container is not installed as a systemd service; you start it manually. For auto-start and restarts, install it as a systemd Quadlet user service instead: 
./setup-podman.sh --quadlet
(Or set FASED_PODMAN_QUADLET=1; use --container to install only the container and launch script.) 2. Start gateway (manual, for quick smoke testing): 
./scripts/run-fased-podman.sh launch
3. Optional CLI onboarding (host/runtime repair or scripted setup): 
./scripts/run-fased-podman.sh launch setup
Then open http://localhost:18789/ and use the token from ~fased/.fased/.env (or the value printed by setup). Finish normal setup in the Control UI from the selected Agent:
  • Agent > Models for model provider auth and model roles
  • Chat for the first working message
  • Agent > Channels for Telegram, Discord, WhatsApp, and other chat routes
  • Agent > Services for web/search, GitHub, Gmail, and other API connectors

​
Systemd (Quadlet, optional)

If you ran ./setup-podman.sh --quadlet (or FASED_PODMAN_QUADLET=1), a Podman Quadlet unit is installed so the gateway runs as a systemd user service for the fased user. The service is enabled and started at the end of setup.
  • Start: sudo systemctl --machine fased@ --user start fased.service
  • Stop: sudo systemctl --machine fased@ --user stop fased.service
  • Status: sudo systemctl --machine fased@ --user status fased.service
  • Logs: sudo journalctl --machine fased@ --user -u fased.service -f
The quadlet file lives at ~fased/.config/containers/systemd/fased.container. To change ports or env, edit that file (or the .env it sources), then sudo systemctl --machine fased@ --user daemon-reload and restart the service. On boot, the service starts automatically if lingering is enabled for fased (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 fased user (non-login)

setup-podman.sh creates a dedicated system user fased:
  • Shell: nologin — no interactive login; reduces attack surface.
  • Home: e.g. /home/fased — holds ~/.fased (config, workspace) and the launch script run-fased-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: 
    fased:100000:65536
    Then start the gateway as that user (e.g. from cron or systemd): 
    sudo -u fased /home/fased/run-fased-podman.sh
sudo -u fased /home/fased/run-fased-podman.sh setup
  • Config: Only fased and root can access /home/fased/.fased. To edit config: use the Control UI once the gateway is running, or sudo -u fased $EDITOR /home/fased/.fased/fased.json.

​
Environment and config

  • Token: Stored in ~fased/.fased/.env as FASED_GATEWAY_TOKEN. setup-podman.sh and run-fased-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 Fased env vars.
  • Host ports: By default the script maps 18789 (gateway) and 18790 (bridge). Override the host port mapping with FASED_PODMAN_GATEWAY_HOST_PORT and FASED_PODMAN_BRIDGE_HOST_PORT when launching.
  • Gateway bind: By default, run-fased-podman.sh starts the gateway with --bind loopback for local-only access. To expose on LAN, set FASED_GATEWAY_BIND=lan and configure gateway.controlUi.allowedOrigins (or explicitly enable host-header fallback) in fased.json.
  • Paths: Host config and workspace default to ~fased/.fased and ~fased/.fased/workspace. Override the host paths used by the launch script with FASED_CONFIG_DIR and FASED_WORKSPACE_DIR.

​
Useful commands

  • Logs: With quadlet: sudo journalctl --machine fased@ --user -u fased.service -f. With script: sudo -u fased podman logs -f fased
  • Stop: With quadlet: sudo systemctl --machine fased@ --user stop fased.service. With script: sudo -u fased podman stop fased
  • Start again: With quadlet: sudo systemctl --machine fased@ --user start fased.service. With script: re-run the launch script or podman start fased
  • Remove container: sudo -u fased podman rm -f fased — 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 FASED_CONFIG_DIR and FASED_WORKSPACE_DIR are owned by that user.
  • Gateway start blocked (missing gateway.mode=local): Ensure ~fased/.fased/fased.json exists and sets gateway.mode="local". setup-podman.sh creates this file if missing.
  • Rootless Podman fails for user fased: Check /etc/subuid and /etc/subgid contain a line for fased (e.g. fased: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 fased.
  • Script not found when running as fased: Ensure setup-podman.sh was run so that run-fased-podman.sh is copied to fased’s home (e.g. /home/fased/run-fased-podman.sh).
  • Quadlet service not found or fails to start: Run sudo systemctl --machine fased@ --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 fased user): build the image, create ~/.fased/.env with FASED_GATEWAY_TOKEN, and run the container with --userns=keep-id and mounts to your ~/.fased. The launch script is designed for the fased-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 fased user so config and process are isolated.