Comment 3 for bug 1466817

Hey Kennan, I've been testing this out and I've hit both of your issues and a couple more.

What I've tested:
1) fedora-21-atomic, using swarm:latest image for swarm-agent and swarm-manager containers
2) fedora-21-atomic, using swarm:0.2.0 image for swarm-agent and swarm-manager containers
3) fedora-22-atomic, using swarm:latest image for swarm-containers
4) fedora-22-atomic, using dockerswarm/swarm image for swarm-containers

Here are the issues I've hit in each case:
1) unsupported version of Docker engine
2) no issues, container-create, container-list, container-start, container-logs seem to be working
3) hit original issue from https://github.com/docker/swarm/issues/781
4) swarm containers started, container create wouldn't work with 'cirros' image, had to use 'docker.io/cirros', this works, but then container list appears to break.

I've also done some digging on the last two issues:
3) This appears to be caused by how 1.6.0 handles images built with 'FROM scratch', I can build a swarm image with FROM debian and it works fine, same with the dockerswarm/swarm image build with FROM golang. Could have something to do with the xfs driver.
4) It appears there might be some odd interactions between swarm and the image string including 'docker.io.' I can quite figure out where that's coming from. I don't see it when I install 1.6.0 on a test box...

For now, I think our best option is to pin the swarm containers at 0.2.0 so that the existing template works with our current image. Then start working towards fixing the issues we hit with fedora-22-atomic. But, I'd definitely like some input on that decision.