nmoray f978b2bb53 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 16:36:09 -07:00
..
cli	modify commands using utilities_common.cli.run_command and advance sonic-utilities submodule on master (#15193)	2023-06-05 17:08:13 +08:00
cli-plugin-tests	[macsec]: show macsec: add --profile option, include profile name in show command output (#13940)	2023-04-27 08:51:28 -07:00
etc	[MACsec]: Set MACsec feature to be auto-start (#6678)	2021-02-23 13:22:45 -08:00
critical_processes	[MACsec]: Set MACsec feature to be auto-start (#6678)	2021-02-23 13:22:45 -08:00
Dockerfile.j2	[infra] Support syslog rate limit configuration (#12490)	2022-12-20 10:53:58 +02:00
start.sh	Timezone sync issue between the host and containers (#14000)	2023-06-25 16:36:09 -07:00
supervisord.conf	Timezone sync issue between the host and containers (#14000)	2023-06-25 16:36:09 -07:00