## Summary <!-- Briefly summarize the bug --> ## Steps to reproduce create a docker runner, set security-opt to ['seccomp=/path/to/seccomp.json'], then the runner cannot start up. ## Actual behavior `seccomp` only accept `unconfined` or a inline json string. ## Expected behavior should worked as docker cli, a path to a seccomp profile json file should be loaded. <!-- What you should see instead --> ## Relevant logs and/or screenshots <!-- Paste the job logs inside of the code blocks (```) below so it would be easier to read. --> <details> <summary> job log </summary> ```sh prepare environment: Error response from daemon: linux seccomp: Decoding seccomp profile failed: invalid character '/' looking for beginning of value (docker.go:817:0s).``` </details> ## Environment description <!-- Are you using shared Runners on GitLab.com? Or is it a custom installation? Which executors are used? Please also provide the versions of related tools like `docker info` if you are using the Docker executor. --> <!-- Please add the contents of `config.toml` inside of the code blocks (```) below, remember to remove any secret tokens! --> <details> <summary> config.toml contents </summary> ```toml Add your configuration here ``` </details> ### Used GitLab Runner version <!-- Please run and paste the output of `gitlab-runner --version`. If you are using a Runner where you don't have access to, please paste at least the first lines the from build log, like: ``` Running with gitlab-ci-multi-runner 1.4.2 (bcc1794) Using Docker executor with image golang:1.8 ... ``` --> 13.5.0 ## Possible fixes <!-- (If you can, link to the line of code that might be responsible for the problem) ---> similar to [this](https://github.com/hashicorp/nomad/pull/7554) patch