add a warning on how to work with sysprep #671
Conversation
emuus
left a comment
emuus
left a comment
There was a problem hiding this comment.
I would suggest the following re-write of the first sentence
|
|
||
| .. image:: /images/install-profile-windowsfp3.png | ||
|
|
||
| .. warning:: For now, please do not select to run sysprep, if the target cloud platform injects CloudBase-Init during its import process, for example, on K5. If you want to run sysprep, run sysprep after the import process has finished. |
There was a problem hiding this comment.
To avoid possible conflicts we recommend you avoid running sysprep, particularly if the target cloud platform injects CloudBase-Init during its import process (this is the case for example on K5).
There was a problem hiding this comment.
For K5 platform, running sysprep is not recommended due to a conflict with CloudBase-Init. You can run sysprep on the instance after publication if needed.
There was a problem hiding this comment.
To avoid possible conflicts we recommend you avoid running sysprep, particularly if the target cloud platform injects CloudBase-Init during its import process (this is the case for example on K5). You can run sysprep on the instance after publication if needed.
There was a problem hiding this comment.
Maybe you can make another commit directly? I think the wording is a bit long but it's fine :)
There was a problem hiding this comment.
Your last proposition is ok for me
3 participants
This warning gives users the instruction on how to work with sysprep, especially when cloudbase-init is injected by the target platform. In mid- and long-term, the issue will be fixed programatically. For now, users are advised not to run sysprep by UForge to avoid possible conflicts with cloudbase-init.