Ubuntu
intel-microcode package

  1. Zesty (17.04)
  2. Bug #1700373
  3. Comment #29

Comment 29 for bug 1700373

Revision history for this message
Uqbar (uqbar) wrote : Re: Please update microcode to version 20170511 on all supported platforms

Maybe mine is just wishful thinking, but microcode update is hardware initialization, containers boot is software. The former should always happen before the latter.

If you have all this computing infrastructure (hypervisors+guests+containers) then it'd be easy to replicate a container on another (virtual) machine and test the new microcode.
This should be done for any update, not just microcode. An apache update could break your web application. Couldn't it?