Red Hat Ecosystem Catalog - Help
  • Using the Red Hat Ecosystem Catalog
  • Hardware
  • About hardware certification
  • Exploring certified hardware
  • Getting support
  • Software
  • Exploring certified software
  • Product details
  • OpenShift operators
  • Cloud-native network functions (CNF)
  • Vulnerability scanners
  • OpenStack infrastructure
  • Standalone applications
  • Container Images
    • Container security
    • Container Health Index for Red Hat Content
    • Container image details
      • Container image types
      • Image tags and versions
      • Container privileges
      • Container image release categories
    • Images from third parties
    • Downloading images
    • Getting support
  • CLOUD
  • Exploring certified cloud providers
    • Browse and search cloud providers
Powered by GitBook
On this page
  1. Container Images
  2. Container image details

Container privileges

How do containers differ in terms of how they are run?

PreviousImage tags and versionsNextContainer image release categories

Last updated 5 years ago

Red Hat defines some container images based not on what they provide, but on how they run.

are designed to run with extra privileges (such as access to the host filesystem, devices, user account, IPC, and so on) to a container’s host system. With that privilege, the container can manage or otherwise access the host system directly.

are those that are configured to run without the docker service, allowing them to either start before the docker service or run on systems that don’t include the docker service. System containers typically use systemd unit files and the runc command to start, stop, and manage those containers.

Super Privileged Container (SPC) images
System Container images