Details
https://docs.docker.com/articles/basics/#bind-docker-to-another-hostport-or-a-unix-socket
2.https://github.com/YungSang/fedora-atomic-packer/blob/master/oem/docker.socket
3.http://daviddaeschler.com/2014/12/14/centos-7rhel-7-and-docker-containers-on-boot/
Solution
Step 1- Find out the file location-systemctl show -p FragmentPath docker.socketStep 2- If the file does not exist, this recommendation is not applicable. If the file exists,
execute the below command with the correct file path to set the ownership and group
ownership for the file to ‘root’.For example,
chown root-root /usr/lib/systemd/system/docker.socketImpact-None.Default Value-This file may not be present on the system. In that case, this recommendation is not
applicable. By default, if the file is present, the ownership and group-ownership for this file
is correctly set to ‘root’.
Supportive Information
The following resource is also helpful.
This security hardening control applies to the following category of controls within NIST 800-53: Configuration Management.This control applies to the following type of system Unix.