Docker Community Forums

Share and learn in the Docker community.

Latest update breaks weave

(Anandkumarpatel) #1

Expected behavior

~$ weave launch

Actual behavior

~$ weave launch
sh: can’t create /proc/sys/net/ipv4/neigh/weave/base_reachable_time: Read-only file system


this worked with
Version 1.10.3-beta5 (build: 5049) e41de947f55a40399da0ddb109d1683013dbaed5
but breaks with latest

  • the output of:

    • pinata diagnose -u on OSX
      OS X: version 10.11.3 (build: 15D21) version v1.10.3-beta5
      Running diagnostic tests:
      [OK] docker-cli
      [OK] Moby booted
      [OK] driver.amd64-linux
      [OK] vmnetd
      [OK] lofs
      [OK] osxfs
      [OK] db
      [OK] slirp
      [OK] menubar
      [OK] environment
      [OK] Docker
      [OK] VT-x
      Docker logs are being collected into /tmp/20160406-005153.tar.gz.
      Your unique id in bugsnag is: 4310E637-A862-4079-924D-434C2066612B
      Please quote this in all correspondence.
  • host distribution and version
    OSX 10.11.x

Steps to reproduce the behavior

  1. sudo curl -L -o /usr/local/bin/weave
  2. sudo chmod a+x /usr/local/bin/weave
  3. weave launch

(Justin Cormack) #2

The latest update ships with docker 1.11.0-rc3, which uses runc, and this has potentially made some changes that could affect this - I think this is the most likely source of this difference. Can you test on another 1.11.0-rc3 system eg Linux and see if this is the same and if so file an issue on

(Justin Cormack) #3

Apparently this is a known issue, expected to be fixed in docker-1.11.0-rc4. The next release of docker for mac is planned to have 1.11.0 final, so this should be resolved next week.

(Justin Cormack) #4

It is this pull request that will be merged for -rc4