In stack create view, better handle failed deployment when container OS doesn't match host

[ghost]

Is your feature request related to a problem? Please describe.
In the stack creation view on windows, if you try to deploy a stack with an image that doesn't match the host, then deployment will look like it failed with an error that the image doesn't match host OS & you won't be redirected to the stacks list view. What really happened is the container will be stuck in a created state and we will show a limited stack with the name you chose.

Describe the solution you'd like
Not sure on the ideal solution here, maybe we could disable the deploy button > show a warning message in the stack creation view for the user about the container OS after it fails > clean up the created container > then enable the deploy button to allow the user to correct error and deploy again from the stacks view without losing their yml definition