-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
time in containers is 1 hour behind #49
Comments
This won't be easy to fix globally as some of the containers do not even have tzdata package installed, but the ones that have offer an environmental variable to be set according to your time zone. What does that mean? When you open /LMDS/docker-compose.yml file you will see containers definition there, some of them have "TZ=UTC" you could change that to i.e. "TZ=Europe/London" - depending on where you are, save it and run "docker-compose up -d" again, this will rebuild container setting your timezone on the container. I would suggest you research timezoning on Docker as there is more to that than I just wrote above. |
I suppose the question is does it matter what the time zone is inside the container? Example, if I set a schedule within sabnzbd will that schedule use the current time (set on the pi) or the wrong time (set in the container) |
It does not matter that much but the schedule set on the container will use
container time.
…On Fri, Aug 19, 2022 at 8:49 AM chenks ***@***.***> wrote:
I suppose the question is does it matter what the time zone is inside the
container?
Example, if I set a schedule within sabnzbd will that schedule use the
current time (set on the pi) or the wrong time (set in the container)
—
Reply to this email directly, view it on GitHub
<#49 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ARFVEPTAS77HXKUNA3ZWKALVZ44BDANCNFSM55VGKRNA>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
i changed the TZ in all the containers i have running to Europe/London using portainer to edit the container variables then re-deploy it from protainer. |
i've noticed that the time inside all the created containers are 1 hour behind the actual time here.
example, i connected to the console on the radarr and sonarr containers and ran
the current time here is 09:05m which at the moment is GMT+1 (or BST).
now, i could just manually adjust the time in each container, but then i guess the next time the clocks change it'll be wrong again.
is there something system wide i can do so that the containers are always at the correct time?
The time set on the Pi is correct. and it set to the correct timezone
The text was updated successfully, but these errors were encountered: