Articles in this section

Which Containers on LiveEdge Max are part of the core OS?

  • Updated
Follow

This article applies to Videon's LiveEdge Max, LiveEdge Max 2, EZ Max, and EZ Max 2 products.

 

With the LiveEdge Max being a Docker-container-based platform, the "Containers" tab in LiveEdge Cloud displays not only the add-on Docker container(s) installed on the device but also the core OS Docker containers. This article is aimed at helping users understand the key differences between these containers.

Identifying Core OS Containers

The containers that are essential to the OS on LiveEdge Max can be distinguished by their naming patterns:

  • Container Name: Core OS containers will have a name starting with videon-...
  • Image Name: Their corresponding image names will start with spyro-...

Any containers with different naming conventions, such as the HTML5 graphics renderer, are considered add-ons.

Example of a Core OS Container

An example of a container that is part of the core OS is:

  • Container Name:

    videon-api-proxy

    This container hosts Videon’s API proxy as part of the core OS.

  • Image:

    spyro-api-proxy:stable-latest

    This pattern of naming is consistent across all core OS containers on LiveEdge Max.

Example List of Core OS Containers


Example of an Add-On Container

In contrast, add-on containers do not follow the same naming pattern and are used for additional features that are not part of the core OS. An example of an add-on container is:

  • Container Name:

    html5-ch1

  • Image:

    videonlabs/html5-graphics-renderer:0.7.5

Add-on containers provide extra functionality and can be installed or removed without affecting the core system operations.

If you have any further questions or need assistance, feel free to reach out to our support team at techsupport@videonlabs.com.

 

Related articles