a1d30e3aa0
Remove Python 2 package installation from the base image. For container builds, reference Python 2 packages only if we're not building for Bullseye. For libyang, don't build Python 2 bindings at all, since they don't seem to be used. Signed-off-by: Saikrishna Arcot <sarcot@microsoft.com>
55 lines
2.2 KiB
Makefile
55 lines
2.2 KiB
Makefile
# docker image for virtual switch based sonic docker image
|
|
|
|
DOCKER_SONIC_VS = docker-sonic-vs.gz
|
|
$(DOCKER_SONIC_VS)_PATH = $(PLATFORM_PATH)/docker-sonic-vs
|
|
$(DOCKER_SONIC_VS)_DEPENDS += $(SWSS) \
|
|
$(SYNCD_VS) \
|
|
$(PYTHON_SWSSCOMMON) \
|
|
$(PYTHON3_SWSSCOMMON) \
|
|
$(LIBTEAMDCTL) \
|
|
$(LIBTEAM_UTILS) \
|
|
$(SONIC_DEVICE_DATA) \
|
|
$(LIBYANG) \
|
|
$(LIBYANG_CPP) \
|
|
$(LIBYANG_PY3) \
|
|
$(SONIC_UTILITIES_DATA) \
|
|
$(SONIC_HOST_SERVICES_DATA)
|
|
|
|
# swsssdk is a dependency of sonic-py-common
|
|
# TODO: sonic-py-common should depend on swsscommon instead
|
|
$(DOCKER_SONIC_VS)_PYTHON_WHEELS += $(SWSSSDK_PY3) \
|
|
$(SONIC_PY_COMMON_PY3) \
|
|
$(SONIC_PLATFORM_COMMON_PY3) \
|
|
$(SONIC_YANG_MODELS_PY3) \
|
|
$(SONIC_YANG_MGMT_PY3) \
|
|
$(SONIC_UTILITIES_PY3) \
|
|
$(SONIC_HOST_SERVICES_PY3)
|
|
|
|
ifeq ($(INSTALL_DEBUG_TOOLS), y)
|
|
$(DOCKER_SONIC_VS)_DEPENDS += $(SWSS_DBG) \
|
|
$(LIBSWSSCOMMON_DBG) \
|
|
$(LIBSAIREDIS_DBG) \
|
|
$(LIBSAIVS_DBG) \
|
|
$(SYNCD_VS_DBG)
|
|
endif
|
|
|
|
ifeq ($(SONIC_ROUTING_STACK), frr)
|
|
$(DOCKER_SONIC_VS)_DEPENDS += $(FRR)
|
|
else
|
|
$(DOCKER_SONIC_VS)_DEPENDS += $(GOBGP)
|
|
endif
|
|
|
|
$(DOCKER_SONIC_VS)_FILES += $(CONFIGDB_LOAD_SCRIPT) \
|
|
$(ARP_UPDATE_SCRIPT) \
|
|
$(ARP_UPDATE_VARS_TEMPLATE) \
|
|
$(BUFFERS_CONFIG_TEMPLATE) \
|
|
$(QOS_CONFIG_TEMPLATE) \
|
|
$(SONIC_VERSION) \
|
|
$(UPDATE_CHASSISDB_CONFIG_SCRIPT) \
|
|
$(COPP_CONFIG_TEMPLATE)
|
|
|
|
$(DOCKER_SONIC_VS)_LOAD_DOCKERS += $(DOCKER_CONFIG_ENGINE_BUSTER)
|
|
SONIC_DOCKER_IMAGES += $(DOCKER_SONIC_VS)
|
|
|
|
SONIC_BUSTER_DOCKERS += $(DOCKER_SONIC_VS)
|