skip to main content
Close Icon We use cookies to improve your website experience.  To learn about our use of cookies and how you can manage your cookie settings, please see our Cookie Policy.  By continuing to use the website, you consent to our use of cookies.
Global Search Configuration


With containers, the role of the OS is important, and we focus here on the Linux OS, as containers cannot be simply moved around without consideration to the OS and version the microservice was built on and the container host OS and version.


  • A great advantage of the microservices architecture is its polyglot nature, and we can take advantage of that by introducing a simple rule to ensure OS sanity: no matter which OS the container's base image was built on, it must run in a host with matching kernel OS and version.

Features and Benefits

  • Learn to deploy containers consistent with OS across base image and host kernel.
  • Understand the challenges with container network controllers.

Key questions answered

  • How can developers ensure containers do not run into OS inconsistencies during deployment?
  • What is the impact of the GPL license on containerization and microservices architecture?

Table of contents

Ovum view

  • Summary
  • Linux distros have library incompatibilities
  • Polyglot: a pattern for mixing container OSs in the environment
  • A container type for the right base image
  • The GPL license was not designed for a container world
  • Container network controllers still have challenges


  • Acknowledgement
  • Author

Recommended Articles


Have any questions? Speak to a Specialist

Europe, Middle East & Africa team: +44 7771 980316

Asia-Pacific team: +61 (0)3 960 16700

US team: +1 212-652-5335

Email us at

You can also contact your named/allocated Client Services Executive using their direct dial.
PR enquiries - Email us at

Contact marketing -

Already an Ovum client? Login to the Knowledge Center now