| Swarm is not far from my dream deploy solution, but here are some points that might be better, some of them being already better in uncloud I think: - energy in the community is low, it's hard to find an active discussion channel of swarm users - swarm does not support the complete compose file format. This is really annoying - sometimes, deploys fail for unclear reasons (eg a network was not found, but why as it's defined in the compose file?) and work the next try. This is never lead to problems, but doesn't feel right - working with authenticate/custom registries is somewhat cumbersome - having to work with registries to have the same image deployed on all nodes is sometimes annoying. It could be cool to have images spreading across nodes. - there's no contact between devs and users. I've just discovered uncloud and I've had more contact with its devs here than in years of using swarm! - the firewalling is not always clear/clean - logs accessibility (service vs container) and containers identification: when a container fails to start, it's sometimes harder than needed to debug (esp when it is because the image is not available) |