Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
1
Merge Requests
1
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
gitlab-ce
Commits
511e67e5
Commit
511e67e5
authored
Jun 21, 2019
by
Achilleas Pipinellis
Committed by
Mike Lewis
Jun 21, 2019
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Mention Container Scanning NFS bug and how to fix it
parent
44db3418
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
20 additions
and
0 deletions
+20
-0
doc/user/application_security/container_scanning/index.md
doc/user/application_security/container_scanning/index.md
+20
-0
No files found.
doc/user/application_security/container_scanning/index.md
View file @
511e67e5
...
...
@@ -40,6 +40,9 @@ To enable Container Scanning in your pipeline, you need:
[
`kubernetes`
](
https://docs.gitlab.com/runner/install/kubernetes.html#running-privileged-containers-for-the-runners
)
executor running in privileged mode. If you're using the shared Runners on GitLab.com,
this is enabled by default.
-
Docker
`18.09.03`
or higher installed on the machine where the Runners are
running. If you're using the shared Runners on GitLab.com, this is already
the case.
-
To
[
build and push
](
../../../ci/docker/using_docker_build.md#container-registry-examples
)
your Docker image to your project's
[
Container Registry
](
../../project/container_registry.md
)
.
The name of the Docker image should match the following scheme:
...
...
@@ -202,3 +205,20 @@ vulnerabilities in your groups and projects. Read more about the
Once a vulnerability is found, you can interact with it. Read more on how to
[
interact with the vulnerabilities
](
../index.md#interacting-with-the-vulnerabilities
)
.
## Troubleshooting
### docker: Error response from daemon: failed to copy xattrs
When the GitLab Runner uses the Docker executor and NFS is used
(e.g.,
`/var/lib/docker`
is on an NFS mount), Container Scanning might fail with
an error like the following:
```
docker: Error response from daemon: failed to copy xattrs: failed to set xattr "security.selinux" on /path/to/file: operation not supported.
```
This is a result of a bug in Docker which is now
[
fixed
](
https://github.com/containerd/continuity/pull/138
"fs: add WithAllowXAttrErrors CopyOpt"
)
.
To prevent the error, ensure the Docker version that the Runner is using is
`18.09.03`
or higher. For more information, see
[
issue #10241
](
https://gitlab.com/gitlab-org/gitlab-ee/issues/10241
"Investigate why Container Scanning is not working with NFS mounts"
)
.
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment