Privileged=true prevents shared library being opened

General Discussions
#1

Hi All,

I’ve got a container that acts as a print server for a USB connected
printer that was previously working on an Arch Linux host, but fails on
an Ubuntu 16.04 host.

The error message when starting cupsd is:

/usr/sbin/cupsd: error while loading shared libraries: libcupsmime.so.1:
cannot open shared object file: No such file or directory

The problem only occurs when the --privileged flag is present. Simply
removing --privileged=true allows cupsd to start successfully, but
causes the print service to fail (without any error message that I can
find).

The run command that worked on Arch Linux is:

$ docker run -d --privileged=true -p 6631:631/tcp -v /dev/bus/usb:/dev/bus/usb --name lbp6020 lbp6020

Looking at the documentation there’s no obvious connection between
–privileged (which affects the containers access to devices) and
loading a shared library.

Any suggestions?

Thanks very much,
Alistair

#2

I’ve had the same problem attempting to run the evince pdf document viewer inside a privileged image:

$ evince
evince: error while loading shared libraries: libevdocument3.so.4: cannot open shared object file: Permission denied

Cheers,
Alistair