Bug 1312947 - [RFE] make container time zone match the one of the node
Summary: [RFE] make container time zone match the one of the node
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: RFE
Version: 3.1.0
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: ---
: ---
Assignee: Derek Carr
QA Contact: Johnny Liu
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-29 15:25 UTC by Evgheni Dereveanchin
Modified: 2023-10-06 17:32 UTC (History)
25 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-03-12 13:54:36 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 2567961 0 None None None 2020-06-19 01:58:23 UTC

Description Evgheni Dereveanchin 2016-02-29 15:25:36 UTC
Description of request:

Currently containers may have random time zones based on the imaged used. This request is to allow setting a timezone for all containers for ease of auditing and maintenance of containers. An option would be to mount /etc/localtime into all containers so that their time zones match the node's time zone

Version-Release number of selected component (if applicable):
3.1.1

Comment 3 Daniel Walsh 2016-07-02 13:39:16 UTC
The problem with always setting the /etc/localtime into the container, is that it assumes that this means something to the content inside of the container.  For this reason docker upstream has been reluctant to accept patches making this so.  

You can simply volume mount in /etc/localtime and hope for the best.

-v /etc/localtime:/etc/localtime

I suppose we could do this at the higher level tools.  Or at least add a config option to do this.

Comment 4 Chris Pitman 2016-07-13 01:09:03 UTC
Asking users to mount in /etc/timezone also means that all users and containers have to be able to do host mounts, which we are generally restricting in OSCP deployments.

Comment 5 Daniel Walsh 2016-07-13 10:21:14 UTC
Can't we make OSCP do this automatically then?

Comment 32 Eric Rich 2018-03-12 13:54:36 UTC
This bug has been identified as a dated (created more than 3 months ago) bug. 
This bug has been triaged (has a trello card linked to it), or reviewed by Engineering/PM and has been put into the product backlog, 
however this bug has not been slated for a currently planned release (3.9, 3.10 or 3.11), which cover our releases for the rest of the calendar year. 

As a result of this bugs age, state on the current roadmap and PM Score (being below 70), this bug is being Closed - Differed, 
as it is currently not part of the products immediate priorities.

Please see: https://docs.google.com/document/d/1zdqF4rB3ea8GmVIZ7qWCVYUaQ7-EexUrQEF0MTwdDkw/edit for more details.

Comment 33 Frantisek Kluknavsky 2018-04-17 14:48:19 UTC
Some useful hints are also in bug 1399749.


Note You need to log in before you can comment on or make changes to this bug.