This page describes how to run various NONRTRIC function sin functions in Docker.

All components of the Non-RT RIC In this sample deployment all NONRTRIC components run as docker containers and communicate via a private docker network with container ports, where ports are also available on localhost.

...

Project Requirements

• docker and docker-compose (latest)

• curl (or similar)
• Additional optional requirements if using the "Helm Manager" function
  • kubernetes v1.19+
  • kubectl with admin access to kubernetes (e.g., minikube, docker-desktop kubernetes etc) 
  • helm with access to kubernetes - this is only applicable when running the Helm Manager example operations 
• Addition optional requirement if using the "DMaaP Adapter" or "DMaap Mediatiotor Mediator Producer" services
  • DMaaP MR (See: Deploy DMaaP message router in nonrtric)
  • Kafka kafka (latest) - only for DMaaP Adpter Adapter Service, and optional

Images

...

In general, there is no need to build the images manually unless there are code changes made by the user, so release images should be used. Instruction on how to build all components, see. Release H - Build.

The run commands throughout this page uses the release images and tags. Replace the release images/tags in the container run commands in the instructions if manually-built snapshot images are desired. 

H Release - Images & Tags

• H Release - Docker Images
  

Ports

The following ports will be allocated and exposed to localhost for each component. If other port(s) are desired, then the ports need to be replaced in the container run commands in the instructions further below.

...