What container images make up Verint Community?

Community 14 is composed of five product images:

Prerequisites

•  How do I install Verint Community? 

Containers

Community Containers

•  Web: serves HTTP requests and the main application UI
•  Job: runs background tasks outside the web process
•  Search: provides Solr cores used by Community search
•  Infra: provides distributed cache and message bus services used by Community
•  Installer: performs first-time installation and later upgrades against the databases on stack startups.

Dependency containers from publicly-available images

• database: Microsoft SQL Server
  • Optional: For ease of installation (especially for local testing and development), the sample stack pulls Microsoft's own SQL Server container. While SQL Server is required in some form, it is not required to use a containerized instance.
• telemetry: .NET Aspire dashboard
  • Optional, but an OpenTelemetry dashboard is recommended.
• antivirus: ClamAV for file validation
  • Optional, but Community 14 has built-in support for ClamAV.

Usage without Compose

Use Compose  for most local installs. Use these images directly when you need to:

• Integrate Community into your own more customized Compose, Kubernetes, or other orchestration layout
• Customize service placement or scaling
• Understand required dependencies and configuration inputs
• Run only part of the stack for troubleshooting or integration work

Shared Expectations

For a standard Community deployment:

• web and job both need access to the same CFS path.
• web, job, and installer all need database connectivity.
• web and job need Solr and infra.
• installer should run to completion before web and job are considered ready.