June 16, 20179 yr My Zoneminder docker is not getting the time zone passed properly when the docker is updated or restarted: root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name="Zoneminder" --net="br0" --ip="192.168.1.8" --privileged="true" -e TZ="" -e HOST_OS="unRAID" -e "TCP_PORT_80"="80" -e "PUID"="99" -e "PGID"="100" -e "SHMEM"="20%" -v "/mnt/cache/appdata/Zoneminder":"/config":rw -v "/mnt/user/zoneminder/data/":"/var/cache/zoneminder":rw --log-opt max-size=50m --log-opt max-file=1 dlandon/zoneminder 7fe8ad9f33efa1489572d5ed9994e51ade5877b2dc3f97433995a235b9e72549 If I edit the template and restart the docker the ZM environment variable is set properly. This appears to be on only one of my two servers. I don't see this issue on my test server. Any ideas on where to look to solve this problem? Edited June 16, 20179 yr by dlandon
June 16, 20179 yr Author Any docker that is updated does not get the TZ environment variable set. It can be re-created by forcing an update on any docker. This is happening in rc3. I booted rc2 and it is also happening there.
June 18, 20179 yr Was this only happening in special cases? I can't seem to make it happen here. But I didn't use Zoneminder to test though.
June 18, 20179 yr 1 minute ago, saarg said: Was this only happening in special cases? I can't seem to make it happen here. But I didn't use Zoneminder to test though. The updater code did not read properly the time-zone from unRAID. Causing an update of any container with an empty TZ. @dlandion: yeah you need to wait for rc5.
June 18, 20179 yr Author It causes a proiblem on Dockers that use the environment variable TZ to set the time zone. Zoneminder just happens to be one that sets its time zone from the TZ variable. You can make it happen by forcing an update to any Docker and checking the start command line to the Docker. You'll see TZ="" which should be for example TZ="America/New_York" for the eastern time zone.
June 18, 20179 yr Author 9 minutes ago, bonienl said: The updater code did not read properly the time-zone from unRAID. Causing an update of any container with an empty TZ. @dlandion: yeah you need to wait for rc5. I can wait. Just wanted to be sure it was addressed before final. The work around is to edit the template and start the Docker that way.
June 18, 20179 yr 11 minutes ago, dlandon said: It causes a proiblem on Dockers that use the environment variable TZ to set the time zone. Zoneminder just happens to be one that sets its time zone from the TZ variable. You can make it happen by forcing an update to any Docker and checking the start command line to the Docker. You'll see TZ="" which should be for example TZ="America/New_York" for the eastern time zone. I am aware of that, but I had the TZ variable set in the template, so it's not dependent of reading the timezone from unraid. So therefor the bug didn't affect the container I tested with.
Archived
This topic is now archived and is closed to further replies.