On 11/10/2014 03:01 AM, Jim Perrin wrote:
On 11/08/2014 12:40 PM, Aditya Patawari wrote:
Hello,
I just tested out the CentOS-7-x86_64-AtomicHost-20141029_02.qcow2 and found an issue with the cockpit-docker integration. To read the images and containers currently residing on the atomic host, cockpit-agent needs to connect to /var/run/docker.sock to which it does not have permission. I did a "chmod o+rw /var/run/docker.sock" to make it work on my test system. Is this a known issue or should I file a bug somewhere?
I ran into this myself, but I see you've already filed the bug for it. I'm not certain what the root cause of this is, but it is something we'll work to address properly for the next release.
not entirely sure at this point - but it looks like the docker rpm didnt create / setup the right groups in the image build.