sonic-buildimage/dockers/docker-teamd/start.sh

#!/usr/bin/env bash

rm -f /var/run/teamd/*

mkdir -p /var/warmboot/teamd

TZ=$(cat /etc/timezone)
rm -rf /etc/localtime
ln -sf /usr/share/zoneinfo/$TZ /etc/localtime
Revert "[docker-teamd]: Manage teamd and teamsyncd processes with supervisor (#1137)" (#1156) This reverts commit a6edef2fa52f5b7771cc5751cde1a190d96ffa50. The reason to revert this commit is that it breaks the current nightly test as no port channel interfaces are get created after boot. teamd failed to start and complained about 'Cannot allocate memory' possibly due to nlmsg_alloc function failure. Will revert this commit to investigate it further before moving to supervisor. Signed-off-by: Shu0T1an ChenG <shuche@microsoft.com> 2017-11-16 12:30:41 -06:00			`#!/usr/bin/env bash`

[teamd]: Add teammgrd in docker-teamd (#2064) Remove the teamd.j2 templates used for starting the teamd. Add teammgrd instead to manage all port channel related configuration changes. Remove front panel port related configurations in interfaces.j2 templates as well. Remove teamd.sh script and use teammgrd to start all the teamd processes. Remove all the logics in the start.sh script as well. Update the sonic-swss submodule. Signed-off-by: Shu0T1an ChenG <shuche@microsoft.com> 2018-10-19 05:41:53 -05:00			`rm -f /var/run/teamd/*`
Revert "[docker-teamd]: Manage teamd and teamsyncd processes with supervisor (#1137)" (#1156) This reverts commit a6edef2fa52f5b7771cc5751cde1a190d96ffa50. The reason to revert this commit is that it breaks the current nightly test as no port channel interfaces are get created after boot. teamd failed to start and complained about 'Cannot allocate memory' possibly due to nlmsg_alloc function failure. Will revert this commit to investigate it further before moving to supervisor. Signed-off-by: Shu0T1an ChenG <shuche@microsoft.com> 2017-11-16 12:30:41 -06:00
Add /host filesystem into teamd docker (#2235) 2018-11-09 18:14:03 -06:00			`mkdir -p /var/warmboot/teamd`
Timezone sync issue between the host and containers (#14000) #### Why I did it To fix the timezone sync issue between the containers and the host. If a certain timezone has been configured on the host (SONIC) then the expectation is to reflect the same across all the containers. This will fix [Issue:13046](https://github.com/sonic-net/sonic-buildimage/issues/13046). For instance, a PST timezone has been set on the host and if the user checks the link flap logs (inside the FRR), it shows the UTC timestamp. Ideally, it should be PST. 2023-06-25 18:36:09 -05:00
			`TZ=$(cat /etc/timezone)`
			`rm -rf /etc/localtime`
			`ln -sf /usr/share/zoneinfo/$TZ /etc/localtime`