Docker Community Forums

Share and learn in the Docker community.

Dockercloud/network-daemon:1.9.1-cs2 does not properly start weave


(Maxpowa) #1

Continually starts/destroys/repeats the weave container, unable to keep it up for more than a couple seconds.

Log output below repeats every time the container restarts.

bash$ docker logs -tf <network daemon container>

2016-04-16T23:54:30.885865995Z => Using weave version: 1.4.1
2016-04-16T23:54:30.886134700Z => Using docker binary:
2016-04-16T23:54:30.930793566Z Client:
2016-04-16T23:54:30.930830374Z  Version:      1.9.1-cs2
2016-04-16T23:54:30.930838780Z  API version:  1.21
2016-04-16T23:54:30.930845820Z  Go version:   go1.4.3
2016-04-16T23:54:30.930852355Z  Git commit:   4ade326
2016-04-16T23:54:30.931025750Z  Built:        Mon Nov 30 21:56:07 UTC 2015
2016-04-16T23:54:30.931110131Z  OS/Arch:      linux/amd64
2016-04-16T23:54:30.931131666Z
2016-04-16T23:54:30.931150354Z Server:
2016-04-16T23:54:30.931168218Z  Version:      1.9.1-cs2
2016-04-16T23:54:30.931186071Z  API version:  1.21
2016-04-16T23:54:30.931203965Z  Go version:   go1.4.3
2016-04-16T23:54:30.931221444Z  Git commit:   4ade326
2016-04-16T23:54:30.931239071Z  Built:        Mon Nov 30 21:56:07 UTC 2015
2016-04-16T23:54:30.931267166Z  OS/Arch:      linux/amd64
2016-04-16T23:54:30.993169600Z => No weave router version 1.4.1 found
2016-04-16T23:54:31.093981923Z => Setting up weave images
2016-04-16T23:54:31.841987854Z 1.4.1: Pulling from weaveworks/weave
2016-04-16T23:54:31.842042103Z Digest: sha256:1d16f94e97c3b21cf9ceeb42c2acbc8201c680ceb244f3429d82cde68c0e4be3
2016-04-16T23:54:31.854863319Z Status: Image is up to date for weaveworks/weave:1.4.1
2016-04-16T23:54:32.626242352Z 1.4.1: Pulling from weaveworks/weaveexec
2016-04-16T23:54:32.626344718Z Digest: sha256:b042d64e2e12c36cf0cfabe189c5f0ce9d8265862b3e72a9a41047b5929e6dcd
2016-04-16T23:54:32.626374139Z Status: Image is up to date for weaveworks/weaveexec:1.4.1
2016-04-16T23:54:33.543272027Z 1.4.1: Pulling from weaveworks/plugin
2016-04-16T23:54:33.543294106Z Digest: sha256:7817956fb7a9ba3b08b6113bad29c6f2ba789b1c5ebcddf577a5ea625cdda9e7
2016-04-16T23:54:33.546037530Z Status: Image is up to date for weaveworks/plugin:1.4.1
2016-04-16T23:54:33.556973124Z => Resetting weave on the node
2016-04-16T23:54:36.374604866Z => Marking the following private subnets as trusted (unencrypted): none
2016-04-16T23:54:36.374658115Z => Running: weave launch -password XXXXXX
2016-04-16T23:54:36.375229755Z => Peer count: 1
2016-04-16T23:54:39.051701603Z Error response from daemon: Could not find container for entity id 20506c37fd22942852b02a2aaa60c73c86bad57bcb51b20b9b3ee8f0754af464
2016-04-16T23:54:41.055220161Z => Current weave router status
2016-04-16T23:54:41.115404038Z
2016-04-16T23:54:41.169052482Z weave container is not present. Have you launched it?

(Html24koebt) #2

I am getting this too all of a sudden. In a production environment. Bye bye docker cloud.