You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, sealer community has wide adopters all around the industry. Each adopter would try to take advantages of sealer to build, distribute, run distributed application anywhere. While we all know that every software has supportive range of OS distributions. If one verion of OS distribution has not been supported objectively, it would be a waste of time for adoptors on this OS distribution.
Gradually, issue like #1396 would increase more and more.
I propose that sealer community should maintain an OS-compatibility list in GitHub repo. And we could guidance users to read this documentation first when taking a try.
What is more, not only could we main related documentation, but also could we implement some preflight tool, like described in #1370 . This tool does preflight check when sealer firstly runs on an OS distribution. If some condition has not been met, it fails.
With the preflight tool, maybe adopters do not have first read the document, but it would throw issues explicitly showing unsatisfied condition. That would be much better.
I think we should take them into consideration step by step.
The text was updated successfully, but these errors were encountered:
I think this is a very good idea. I mean, it allows sealer users to quickly evaluate the speed of their delivery.
And integrated into preflight tool, users can avoid wasting time on unnecessary compatibility issues.
God, I mean, that's great!
Issue Description
Currently, sealer community has wide adopters all around the industry. Each adopter would try to take advantages of sealer to build, distribute, run distributed application anywhere. While we all know that every software has supportive range of OS distributions. If one verion of OS distribution has not been supported objectively, it would be a waste of time for adoptors on this OS distribution.
Gradually, issue like #1396 would increase more and more.
I propose that sealer community should maintain an OS-compatibility list in GitHub repo. And we could guidance users to read this documentation first when taking a try.
What is more, not only could we main related documentation, but also could we implement some preflight tool, like described in #1370 . This tool does preflight check when sealer firstly runs on an OS distribution. If some condition has not been met, it fails.
With the preflight tool, maybe adopters do not have first read the document, but it would throw issues explicitly showing unsatisfied condition. That would be much better.
I think we should take them into consideration step by step.
The text was updated successfully, but these errors were encountered: