Containers include an application as well as a file system. The file system contains everything needed by the application for its execution: executable, libraries, system tools, configuration files and a runtime environment. Unlike with full virtualization, a container does not have its own operation system. However, independence from the underlying Linux Board Support Package as well as hardware can be realized.
In order to run containers independently of each other and to isolate processes, functions like cgroups and namespaces are used. They use low resources and allow short loading times. Containers are isolated from each other and can only use a few defined interfaces. Migration from one Linux system to another is possible in a very simple and efficient way.
Improved portability and maintenance
Based on runc, LXC and rkt emlix’s container architectures are used in very different industries and areas of application. The interaction across containers within a product allows us to orchestrate for example a safety-critical application, a multimedia GUI application, Java middleware as well as a web server, cloud connectors and third-party software in separately maintained containers of a Linux Board Support Package.
A heavyweight framework like Docker is intentionally being left out, but the scope of functions is realized similarly.
emlix designs, integrates, documents and tests updateable container concepts based on the OpenContainerInitiative (OCI) and similar standards.
Phone +49 (0) 551 / 306 64 - 0
solutions [at] emlix.com