I need a container network? • why to use Weave Net? • How Weave Net works • comparison to other solutions • Demo (rkt & Docker on GCE + Docker for Mac)
runtime built by CoreOS • rkt is somewhat less opinionated then Docker • Docker uses runC, which is similar to rkt • rkt has a simpler architecture • rkt is easier to use as a building block • rkt can run Docker images
without one) • provides unique IP for each container • has simple service discovery built-in • easy to setup and manage • works with all runtimes, as you will see • works the same in any cloud
easy to implement and hard to debug • SRV record or directory lookup • e.g.: Consul, Zookeeper, etcd • wrapping service discovery into proxy config is not optimal and even harder to debug • e.g.: multitude of bespoke code on Github
commands on any host: docker run -d \ —-name=svc-a image docker run -d \ —-name=svc-b image docker run -d alpine ping -c3 svc-a docker run -d alpine ping -c3 scc-b