Azure EFLOW CBL Mariner Size expanded to big footprint

Question

Hi,

Azure EFLOW is based on CBL Mariner OS. The 2.0 is given as small as 67MB however its VM size on the host is about 3,5GB (800MB just as ISO size). Why such big size difference?

thanks

Answer 1

Hi @banto b Greetings! Welcome to Microsoft Q&A forum. Thank you for posting this question here.

That is a good observation. The size difference you notice on the host is due to a few factors which includes the following.

1. The ISO file size only represents the size of the installation media, which contains the necessary files to install the operating system. This does not include any additional files or packages that are installed during the installation process.
2. The actual VM size on the host includes not only the operating system files, but also any additional packages, libraries, and dependencies such as Microsoft update Agent that are required to run the EFLOW service.
3. The VM size on the host may also include additional files and data that are generated during the operation of the EFLOW service, such as log files, configuration files, and user data.
4. Modules installed on Eflow also factor into the space consumption of the total VM. IoT Edge comes with two modules IoT Edge Agent and Edge Hub by default. Any additional modules you may add may also contribute to the space occupied by the VM.

Hope this makes sense. Please let us know if you have any additional questions or need further assistance on this.