ntp service not starting on privilegied mode

[Thomas ttw]

Hi,

It looks like there is an issue with the baseimage when running in privileged mode.
here is how you repeat the problem:

root@server:~# docker run -t -i --privileged phusion/baseimage /bin/bash

root@90572e35c84a:/# apt-get update && apt-get install ntp

root@90572e35c84a:/# service ntp start

 * Starting NTP server ntpd                                         /usr/sbin/ntpd: error while loading shared libraries: libopts.so.25: cannot open shared object file: Permission denied

the file /usr/lib/x86_64-linux-gnu/libopts.so.25.15.0 is 644 and readable even as ntp user.

if you do the same thing without the privileged mode it works fine.

Anybody having an idea of what could be causing the issue ?

Thanks !

[Josh Reichardt]

I am experiencing this same issue.  Did you ever find a solution?

[Matt M]

I ran into the same issue today with Docker 1.5.0 on an Ubuntu 14.04LTS host with the AUFS storage driver explicitly configured (DOCKER_OPTS="--storage-driver=aufs" in /etc/default/docker).

After switching to devicemapper (DOCKER_OPTS="--storage-driver=devicemapper") and restarting the Docker service, I was able to launch a phusion/baseimage instance with --privileged=true and install/start ntpd without any trouble.

(I haven't tried to reproduce this with other storage drivers yet.)

[Jay Kamat]

I have been having this issue for a long time as well, and the solution turned out to be that apparmor was preventing access to ntp on the host machine. Turning off apparmor for ntpd on the host solved this problem, and it now works fine on devicemapper/aufs.