# Teaching lab: ferrix_bgp plus two FRR routers forming a loop, so a prefix
# announced from the web UI travels ferrix -> r1 -> r2 -> ferrix and shows up
# in the "received routes" table with the AS path it collected on the way.
#
#   AS65000 ferrix  10.200.0.1   web UI on http://localhost:8080/statusz
#   AS65001 r1      10.200.0.2   applies community-driven policy
#   AS65002 r2      10.200.0.3   learns only via r1, re-advertises to ferrix
#
# Usage (from the repository root):
#   docker compose -f docs/lab/docker-compose.yml up --build
#
# NOTE: this topology has not been run by the author of this file on the
# machine it was written on (no container runtime was available). Expect to
# adjust image tags and FRR config syntax for the FRR version you pull.
services:
  ferrix:
    build:
      context: ../..
    container_name: ferrix
    volumes:
      - ./ferrix.textpb:/etc/ferrix/server.textpb:ro
    ports:
      - "8080:8080"
    networks:
      lab:
        ipv4_address: 10.200.0.1

  r1:
    image: quay.io/frrouting/frr:10.2.1
    container_name: r1
    privileged: true
    volumes:
      - ./r1:/etc/frr:ro
    networks:
      lab:
        ipv4_address: 10.200.0.2

  r2:
    image: quay.io/frrouting/frr:10.2.1
    container_name: r2
    privileged: true
    volumes:
      - ./r2:/etc/frr:ro
    networks:
      lab:
        ipv4_address: 10.200.0.3

networks:
  lab:
    driver: bridge
    ipam:
      config:
        - subnet: 10.200.0.0/24