- Why I did it The values for config_db "docker_routing_config_mode" are: separated: FRR config generated from ConfigDB, each FRR daemon has its own config file unified: FRR config generated from ConfigDB, single FRR config file split: FRR config not generated from ConfigDB, each FRR daemon has its own config file This commit adds: split-unified: FRR config not generated from ConfigDB, single FRR config file - How I did it In docker_init.sh, when split-unified is used, the FRR configs are not generated from ConfigDB. What's more, "service integrated-vtysh-config" is configured in vtysh.conf. - How to verify it FRR config not overwritten when FRR container starts. Signed-off-by: Arnaud le Taillanter <a.letaillanter@criteo.com> |
||
---|---|---|
.. | ||
docker-base | ||
docker-base-bullseye | ||
docker-base-buster | ||
docker-base-stretch | ||
docker-basic_router | ||
docker-config-engine | ||
docker-config-engine-bullseye | ||
docker-config-engine-buster | ||
docker-config-engine-stretch | ||
docker-database | ||
docker-dhcp-relay | ||
docker-fpm-frr | ||
docker-fpm-gobgp | ||
docker-iccpd | ||
docker-lldp | ||
docker-macsec | ||
docker-mux | ||
docker-nat | ||
docker-orchagent | ||
docker-pde | ||
docker-platform-monitor | ||
docker-ptf | ||
docker-ptf-sai | ||
docker-router-advertiser | ||
docker-sflow | ||
docker-snmp | ||
docker-sonic-mgmt | ||
docker-sonic-mgmt-framework | ||
docker-sonic-p4rt | ||
docker-sonic-restapi | ||
docker-sonic-sdk | ||
docker-sonic-sdk-buildenv | ||
docker-sonic-telemetry | ||
docker-swss-layer-bullseye | ||
docker-swss-layer-buster | ||
docker-teamd | ||
dockerfile-macros.j2 |