0

It seems like chronyd doesn't work in lxc containers. The containers running are not unprivileged. Following is showing up with systemd:

● chronyd.service - NTP client/server
   Loaded: loaded (/usr/lib/systemd/system/chronyd.service; enabled; vendor preset: enabled)
   Active: inactive (dead)
Condition: start condition failed at Fri 2021-02-05 15:12:48 CET; 3s ago
           └─ ConditionCapability=CAP_SYS_TIME was not met
     Docs: man:chronyd(8)
           man:chrony.conf(5)

I would really like to manage the time inside the lxc's not with the host, because it's a lxc cluster and i don't want to mess with the cluster's time. Did somebody already found a workaround for this?

Lorem ipsum
  • 852
  • 3
  • 13
  • 4
    There is no difference. The containers all use the host clock as that is the only clock. You need to rethink your approach to whatever you were trying to do. – Michael Hampton Feb 05 '21 at 14:22
  • Agreed, you want the cluster to use ntp to always be in sync, and the containers will be in sync by themselfs. – Fredrik Feb 06 '21 at 09:34

0 Answers0