-
Notifications
You must be signed in to change notification settings - Fork 3
Add composefs backend #61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -32,7 +32,6 @@ write_files: | |
| content: | | ||
| [crio.network] | ||
| plugin_dirs = [ | ||
| "/opt/cni/bin", | ||
| "/var/lib/cni/bin", | ||
| "/usr/libexec/cni", | ||
| ] | ||
|
|
@@ -75,11 +74,12 @@ runcmd: | |
| - sysctl -w net.ipv4.ip_forward=1 | ||
| - echo 'net.ipv4.ip_forward=1' > /etc/sysctl.d/99-kubernetes.conf | ||
| - mkdir -p /var/lib/kubelet/volumeplugins | ||
| - mkdir -p /var/lib/cni/bin | ||
| - mkdir -p /var/mnt/cluster_images | ||
| - mkdir -p /var/lib/containers/storage | ||
| - systemctl daemon-reload | ||
| - systemctl enable --now var-mnt-cluster_images.mount | ||
| - systemctl enable --now ostree-state-overlay@opt.service | ||
| - systemctl enable --now ostree-state-overlay@opt.service || true | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. issue (bug_risk): Silencing Using |
||
| - systemctl enable --now qemu-guest-agent | ||
| - nmcli connection modify "cloud-init enp2s0" ipv4.dns-search "~{{.ClusterDomain}} {{.ClusterDomain}}" | ||
| - nmcli connection up "cloud-init enp2s0" | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
security (CKV_K8S_16): Container should not be privileged
Privileged containers are containers that have all of the root capabilities of a host machine, allowing access to resources that are not accessible in ordinary containers.
Common uses of privileged containers include: running a Docker daemon inside a Docker container, running a container with direct hardware access, and automating CI/CD tasks in the open-source automation server Jenkins.
Running a container with a privileged flag allows users to have critical access to the host's resources.
If a privileged container is compromised, it does not necessarily entail remote code execution, but it implies that an attacker will be able to run full host root with all of the available capabilities, including CAP_SYS_ADMIN.
Fix
Kubernetes
If true, processes in the privileged containers are essentially equivalent to root on the host.
Default to false.
Source: checkov