Create a Docker authentication record in order to authenticate to a docker running on a Linux host, and scan it for compliance. Unix authentication is required so you'll also need a Unix record for the host running the docker.
This record type is only available in accounts with PC or SCA and is only supported for compliance scans.
- Docker daemon versions 1.9 to 1.13
- Docker Community Edition (CE) version 17.x or later
- Docker Enterprise Edition (EE) version 17.x or later
- CentOS >= 7.x
- Debian >= 8.x
- Oracle Linux >= 6.x
- RHEL >= 7.x
- OpenSUSE >=13.2
- SUSE >= 12.x
- Ubuntu >= 12.04 (LTS)
- Go to Scans > Authentication.
- Check that you have a Unix record already defined for the host running the docker.
- Create a Docker authentication record for the same host. Go to New > Application Records > Docker.
Managers can add authentication records.
Unit Managers must be granted these permissions:
- Manage PC module / Manage SCA module
- Create/edit authentication records/vaults
We need to know where the server is installed (i.e. Docker command). Set the docker command which can connect to the local docker daemon by entering a path to the command, or leave this blank and we'll set to "docker".
If the Docker daemon requires a configuration file to boot up we need to know about this file (i.e. Configuration File). You can enter the path to this file, or leave this blank to let our service auto discover this file. Good to Know - If you leave blank it's possible we can't find the file and this might result in some configurations not found.