Mount directory warmboot in docker gbsyncd (#11852)
Why I did it The directory /var/warmboot as top directory for warmboot feature is also needed in docker gbsyncd. Some vendor SAI might save data under it. Without it, the SAI init/creation API failure has happened on PikeZ platform. How I did it Mount host directory /host/warmboot as /var/warmboot in docker gbsyncd, which is same as what it has done on docker syncd.
This commit is contained in:
parent
9551ca20e7
commit
b722d5f7de
@ -27,6 +27,7 @@ $(DOCKER_GBSYNCD_BRONCOS)_CONTAINER_NAME = gbsyncd
|
|||||||
$(DOCKER_GBSYNCD_BRONCOS)_RUN_OPT += --privileged -t
|
$(DOCKER_GBSYNCD_BRONCOS)_RUN_OPT += --privileged -t
|
||||||
$(DOCKER_GBSYNCD_BRONCOS)_RUN_OPT += -v /host/machine.conf:/etc/machine.conf
|
$(DOCKER_GBSYNCD_BRONCOS)_RUN_OPT += -v /host/machine.conf:/etc/machine.conf
|
||||||
$(DOCKER_GBSYNCD_BRONCOS)_RUN_OPT += -v /etc/sonic:/etc/sonic:ro
|
$(DOCKER_GBSYNCD_BRONCOS)_RUN_OPT += -v /etc/sonic:/etc/sonic:ro
|
||||||
|
$(DOCKER_GBSYNCD_BRONCOS)_RUN_OPT += -v /host/warmboot:/var/warmboot
|
||||||
|
|
||||||
SONIC_ONLINE_DEBS += $(LIBSAI_BRONCOS)
|
SONIC_ONLINE_DEBS += $(LIBSAI_BRONCOS)
|
||||||
|
|
||||||
|
@ -27,3 +27,4 @@ $(DOCKER_GBSYNCD_BASE)_CONTAINER_NAME = gbsyncd
|
|||||||
$(DOCKER_GBSYNCD_BASE)_RUN_OPT += --privileged -t
|
$(DOCKER_GBSYNCD_BASE)_RUN_OPT += --privileged -t
|
||||||
$(DOCKER_GBSYNCD_BASE)_RUN_OPT += -v /host/machine.conf:/etc/machine.conf
|
$(DOCKER_GBSYNCD_BASE)_RUN_OPT += -v /host/machine.conf:/etc/machine.conf
|
||||||
$(DOCKER_GBSYNCD_BASE)_RUN_OPT += -v /etc/sonic:/etc/sonic:ro
|
$(DOCKER_GBSYNCD_BASE)_RUN_OPT += -v /etc/sonic:/etc/sonic:ro
|
||||||
|
$(DOCKER_GBSYNCD_BASE)_RUN_OPT += -v /host/warmboot:/var/warmboot
|
||||||
|
Loading…
Reference in New Issue
Block a user