a common use case would be adding a local docker registry..

i tried but was failing..

can you please add it to the shell scripts and compose file.

thanks

what would be the steps for bare-metals ..
want to setup local env

Hi there -

I setup a Swarm cluster on Azure using this: https://github.com/Azure/azure-quickstart-templates/tree/master/docker-swarm-cluster

and then followed the tutorial/used the compose file in this repo to get a Kubernetes cluster running. I also followed the instructions to setup multi-host networking on my Swarm cluster, and from what I can tell, that is all working.

I'm able to deploy the Wordpress example (and everything says, Ready, status OK, etc etc).

But I have absolutely no idea how to access the thing. Because there's (at least) four layers of networking here: Physcial IP address of the machine (my nodes are on a 192.168.0.0/24 range) which is what my load balancer needs to point to, at the end of the day; the Swarm overlay network (titled "kubernetes", and with an IP range of 10.10.1.0/24); the Swarm bridge network ("docker_gwbridge", in the 172.18.0.0/16 range); and then what --service-cluster-ip-range is set to in the docker-compose file (172.17.17.1/24).

When I expose the port (using Kubernetes NodePort service type)...I can't access anything unless I access the pod directly.

Do you all have any thoughts on how to make this work? Or any possible guidance here? It would be much appreciated.

Thanks for putting this project together!

-Adam

I am trying to start cluster on Ubuntu 14.04.2 LTS and get this error:

$ docker-compose --x-networking -f mesos-marathon-swarm.yml up -d

Creating zookeeper
ERROR: Cannot start container 2e0db99266e13f5f04f6a1bad101b370cf4115f98b5ee73865ba0bb72140e556: subnet sandbox join failed for "10.0.1.0/24": vxlan interface creation failed for subnet "10.0.1.0/24": failed in prefunc: failed to set namespace on link "vxlana8e0a02": invalid argument

docker info:

Containers: 5
Images: 15
Role: primary
Strategy: spread
Filters: health, port, dependency, affinity, constraint
Nodes: 3
 swarm-master: 95.213.200.201:2376
  └ Status: Healthy
  └ Containers: 3
  └ Reserved CPUs: 0 / 1
  └ Reserved Memory: 0 B / 514.6 MiB
  └ Labels: executiondriver=native-0.2, kernelversion=3.13.0-24-generic, operatingsystem=Ubuntu 14.04.2 LTS, provider=vscale, storagedriver=aufs
 swarm-node-01: 95.213.200.214:2376
  └ Status: Healthy
  └ Containers: 1
  └ Reserved CPUs: 0 / 1
  └ Reserved Memory: 0 B / 514.6 MiB
  └ Labels: executiondriver=native-0.2, kernelversion=3.13.0-24-generic, operatingsystem=Ubuntu 14.04.2 LTS, provider=vscale, storagedriver=aufs
 swarm-node-02: 95.213.200.136:2376
  └ Status: Healthy
  └ Containers: 1
  └ Reserved CPUs: 0 / 1
  └ Reserved Memory: 0 B / 514.6 MiB
  └ Labels: executiondriver=native-0.2, kernelversion=3.13.0-24-generic, operatingsystem=Ubuntu 14.04.2 LTS, provider=vscale, storagedriver=aufs
CPUs: 3
Total Memory: 1.508 GiB
Name: swarm-master

root@swarm-master:~# uname -a
Linux swarm-master 3.13.0-24-generic #47-Ubuntu SMP Fri May 2 23:30:00 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

Please help me to resolve this error.

docker/compose#3029

Thus docker-compose --x-networking -f k8s-swarm.yml up won't work.
Need to update README and also update compose yml to version 2, as latest docker-compose would not create network automatically for project with yml version 1.

i suggest to add shipyard