IssueRaiser

When I first starting working with docker I'd use the docker inspect $CONTAINER | grep -i VAR pattern alot until I discovered that y...

When I first starting working with docker I'd use the docker inspect $CONTAINER | grep -i VAR pattern alot until I discovered that you can do use the container name and do go with: docker inspect --format '{{ .NetworkSettings.IPAddress }}' replset1 Service discovery and docker is still a pain point with the technology. Serf [1] and etcd [2] are tools that manages a cluster of services and helps solve the problem described in the article. [1] Serf is by the guys behind Vagrant. - http://www.serfdom.io/ [2] etcd - http://coreos.com/using-coreos/etcd/

Posted by thedevopsguy on Jul 30, 2014, 2:12 PM

Tags

Related issues

Raise real-world problems, find people facing the same issue, and discuss solutions.9,500 issues0 comments

hackernews (Other)

When I first starting working with docker I'd use the docker inspect $CONTAINER | grep -i VAR pattern alot until I discovered that y...

thedevopsguyJul 30, 2014, 2:12 PM

When I first starting working with docker I'd use the docker inspect $CONTAINER | grep -i VAR pattern alot until I discovered that you can do use the container name and do go with: docker inspect --format '{{ .NetworkSettings.IPAddress }}' replset1 Service discovery and docker is still a pain point with the technology. Serf [1] and etcd [2] are tools that manages a cluster of services and helps solve the problem described in the article. [1] Serf is by the guys behind Vagrant. - http://www.serfdom.io/ [2] etcd - http://coreos.com/using-coreos/etcd/

Comments (0)

No comments yet. Start the discussion.

Comment on this issue