---

Subject:	I believe this was a bug
Author:	[Not Specified]
Posted:	2016-03-17 08:23

I believe this was a bug fixed in v5.1.1

---

Subject:	the bug still persisting in 5.1.1
Author:	[Not Specified]
Posted:	2016-03-28 07:51

I'm using v5.1.1 and this problemstill persists.

newbie

---

Subject:	The best approach is to mount
Author:	Jan Garaj
Posted:	2016-03-28 08:13

The best approach is to mount host localtime as container volume:

-v /etc/localtime:/etc/localtime:ro 

But I'm not sure if it's possible with CC.

Devops Monitoring Expert advice: Dockerize/automate/monitor all the things.

DevOps stack: Docker / Kubernetes / Mesos / Zabbix / Zenoss / Grafana / Puppet / Ansible / Vagrant / Terraform / Elasticsearch

---

Subject:	Default container time is UTC
Author:	Jan Garaj
Posted:	2016-03-28 08:41

Default container time is UTC. So you need to pass host OS timezone to the container. Or you can set timezone in app config (probably zope case).

Ref:

https://github.com/docker/docker/issues/3359

Key points:

• containers share the kernel
• the kernel tracks the "current time" (note this is "time", not "timezone"), and it is tracked simply as the "number of seconds since the epoch (1970-01-01 00:00:00 UTC)" (hence the name, "Unix Timestamp")
• userspace (which includes tools like date) has a notion of "timezone", and it usually comes from "/etc/localtime" (but this does sometimes depends on the utility, some read "/etc/timezone" instead, and some update "/etc/localtime" from the contents of "/etc/timezone")

Devops Monitoring Expert advice: Dockerize/automate/monitor all the things.

DevOps stack: Docker / Kubernetes / Mesos / Zabbix / Zenoss / Grafana / Puppet / Ansible / Vagrant / Terraform / Elasticsearch

---

Subject:	serviced service edit
Author:	[Not Specified]
Posted:	2016-03-29 02:30

I'm trying to edit Zenoss.coreservice but thechangesmade won't persist. When I open again in the editor the changes are not there.

serviced service edit Zenoss.core

Am Idoing something wrong

newbie