Red Hat Summit Red Hat SummitApoyoConsolaDesarrolladoresIniciar una pruebaContacto

Este contenido no está disponible en el idioma seleccionado.

Chapter 29. Restricting Application Capabilities Using Seccomp

29.1. Overview
Copiar enlace

Seccomp (secure computing mode) is used to restrict the set of system calls applications can make, allowing cluster administrators greater control over the security of workloads running in OpenShift Container Platform.

Seccomp support is achieved via two annotations in the pod configuration:

  • seccomp.security.alpha.kubernetes.io/pod: profile applies to all containers in the pod that do not override
  • container.seccomp.security.alpha.kubernetes.io/<container_name>: container-specific profile override
Important

Containers are run with unconfined seccomp settings by default.

For detailed design information, refer to the seccomp design document.

29.2. Enabling Seccomp
Copiar enlace

Seccomp is a feature of the Linux kernel. To ensure seccomp is enabled on your system, run: 

$ cat /boot/config-`uname -r` | grep CONFIG_SECCOMP=
CONFIG_SECCOMP=y
Copy to Clipboard Toggle word wrap

29.3. Configuring OpenShift Container Platform for Seccomp
Copiar enlace

A seccomp profile is a json file providing syscalls and the appropriate action to take when a syscall is invoked.

  1. Create the seccomp profile.

    The default profile is sufficient in many cases, but the cluster administrator must define the security constraints of an individual system.

    To create your own custom profile, create a file on every node in the seccomp-profile-root directory.

    If you are using the default docker/default profile, you do not need to create one.

  2. Configure your nodes to use the seccomp-profile-root where your profiles will be stored. In the node-config.yaml via the kubeletArguments: 

    kubeletArguments:
  seccomp-profile-root:
    - "/your/path"
    Copy to Clipboard Toggle word wrap

  3. Restart the node service to apply the changes: 

    # systemctl restart atomic-openshift-node
    Copy to Clipboard Toggle word wrap

  4. In order to control which profiles may be used, and to set the default profile, configure your SCC via the seccompProfiles field. The first profile will be used as a default.

    The allowable formats of the seccompProfiles field include:

    • docker/default: the default profile for the container runtime (no profile required)
    • unconfined: unconfined profile, and disables seccomp

    • localhost/<profile-name>: the profile installed to the node’s local seccomp profile root

      For example, if you are using the default docker/default profile, configure your SCC with: 

      seccompProfiles:
- docker/default
      Copy to Clipboard Toggle word wrap

To ensure pods in your cluster run with a custom profile:

  1. Create the seccomp profile in seccomp-profile-root.

  2. Configure seccomp-profile-root: 

    kubeletArguments:
  seccomp-profile-root:
    - "/your/path"
    Copy to Clipboard Toggle word wrap

  3. Restart the node service to apply the changes: 

    # systemctl restart atomic-openshift-node
    Copy to Clipboard Toggle word wrap

  4. Configure your SCC: 

    seccompProfiles:
- localhost/<profile-name>
    Copy to Clipboard Toggle word wrap
Volver arriba
Red Hat logoGithubredditYoutubeTwitter

Aprender

Pruebe, compre y venda

Comunidades

Acerca de la documentación de Red Hat

Ayudamos a los usuarios de Red Hat a innovar y alcanzar sus objetivos con nuestros productos y servicios con contenido en el que pueden confiar. Explore nuestras recientes actualizaciones.

Hacer que el código abierto sea más inclusivo

Red Hat se compromete a reemplazar el lenguaje problemático en nuestro código, documentación y propiedades web. Para más detalles, consulte el Blog de Red Hat.

Acerca de Red Hat

Ofrecemos soluciones reforzadas que facilitan a las empresas trabajar en plataformas y entornos, desde el centro de datos central hasta el perímetro de la red.

Theme

© 2025 Red Hat