Stay organized with collections
Save and categorize content based on your preferences.
Migration warnings
This page describes the warnings that you might get after you run the
analyze command.
Types of warnings
After you run the analyze command, Migrate to Containers might provide warnings
specific to your migration type.
There are two possible types of warnings:
MigrationBlocker warnings: These warnings block your migration,
and you must address them. You cannot generate the artifacts of a migration
while there are active MigrationBlocker warnings.
Normal warnings: These are non-blocking warnings that you can decide to
address. Even though warnings of type Normal don't block the generation of
artifacts, they might cause the migration process to fail, or cause the migrated
workload to fail when run.
How to read the warnings
If there are warnings, they appear in the warnings.yaml file in the output
directory of the analyze command.
Each warning message contains the following fields:
type: The type of warning, either MigrationBlocker or Normal.
reason: The cause of the warning.
mitigation: The description of the warning and possible actions to
resolve it.
For example, the following is a FileTooBig warning for Linux.
-message:The source VM file-system contains file(s) which are too big to be part of the generated container imagemitigation:Please edit the migration plan to either filter them out, or export them to a data volumereason:FileTooBigtype:MigrationBlocker
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-09-04 UTC."],[],[],null,["# Migration warnings\n==================\n\nThis page describes the warnings that you might get after you run the\n`analyze` command.\n\nTypes of warnings\n-----------------\n\nAfter you run the `analyze` command, Migrate to Containers might provide warnings\nspecific to your migration type.\nThere are two possible types of warnings:\n\n- **`MigrationBlocker` warnings:** These warnings block your migration, and you must address them. You cannot generate the artifacts of a migration while there are active `MigrationBlocker` warnings.\n- **`Normal` warnings:** These are non-blocking warnings that you can decide to address. Even though warnings of type `Normal` don't block the generation of artifacts, they might cause the migration process to fail, or cause the migrated workload to fail when run.\n\nHow to read the warnings\n------------------------\n\nIf there are warnings, they appear in the `warnings.yaml` file in the output\ndirectory of the `analyze` command.\n\nEach warning message contains the following fields:\n\n- **type:** The type of warning, either `MigrationBlocker` or `Normal`.\n- **reason:** The cause of the warning.\n- **mitigation:** The description of the warning and possible actions to resolve it.\n\nFor example, the following is a `FileTooBig` warning for Linux. \n\n - message: The source VM file-system contains file(s) which are too big to be part of the generated container image\n mitigation: Please edit the migration plan to either filter them out, or export them to a data volume\n reason: FileTooBig\n type: MigrationBlocker"]]
