Sebastiaan van Stijn 68e96f88ee Fix daemon.json and daemon --seccomp-profile not accepting "unconfined" ... Commit b237189e6c implemented an option to set the default seccomp profile in the daemon configuration. When that PR was reviewed, it was discussed to have the option accept the path to a custom profile JSON file; https://github.com/moby/moby/pull/26276#issuecomment-253546966 However, in the implementation, the special "unconfined" value was not taken into account. The "unconfined" value is meant to disable seccomp (more factually: run with an empty profile). While it's likely possible to achieve this by creating a file with an an empty (`{}`) profile, and passing the path to that file, it's inconsistent with the `--security-opt seccomp=unconfined` option on `docker run` and `docker create`, which is both confusing, and makes it harder to use (especially on Docker Desktop, where there's no direct access to the VM's filesystem). This patch adds the missing check for the special "unconfined" value. Co-authored-by: Tianon Gravi <admwiggin@gmail.com> Signed-off-by: Sebastiaan van Stijn <github@gone.nl>		2021-08-07 15:40:45 +02:00
..
docker-proxy	Move proxy CLI to main cmd/	2021-06-25 18:01:55 +02:00
dockerd	Fix daemon.json and daemon --seccomp-profile not accepting "unconfined"	2021-08-07 15:40:45 +02:00