error running docker

[on-meetsys]

Hello,

I've followed your readme, but sonm node can not be launched :

docker run --rm -p 10002:10002 -p 10001:10001  sonm/insonmnia sonmhub

docker: Error response from daemon: failed to create endpoint elegant_goodall on network bridge: failed to add the host (vethac43067) <=> sandbox (veth3a8eca5) pair interfaces: operation not supported.

And if I try to run the mining node :

docker run -d --env DOCKER_API_VERSION=1.24 --net=host -v /run:/var/run sonm/insonmnia:alpha3 sonmminer --hubaddress=35.177.238.170:10002

e14ad68223455c3040fd887f9b115e2e221a54c33d939f49ba5ff0dd3c6dd059
docker: Error response from daemon: oci runtime error: container_linux.go:247: starting container process caused "process_linux.go:245: running exec setns process for init caused \"exit status 29\"".

I use a Debian 7.5 wheezy
ports 10001 and 10002 are opened. What could I try ?

Thanks

[noxiouz]

Hi!
Please, show me docker version

[on-meetsys]

Here is it

Containers: 4
 Running: 0
 Paused: 0
 Stopped: 4
Images: 2
Server Version: 17.03.1-ce
Storage Driver: devicemapper
 Pool Name: docker-8:1-4593036-pool
 Pool Blocksize: 65.54 kB
 Base Device Size: 10.74 GB
 Backing Filesystem: xfs
 Data file: /dev/loop0
 Metadata file: /dev/loop1
 Data Space Used: 1.032 GB
 Data Space Total: 107.4 GB
 Data Space Available: 106.3 GB
 Metadata Space Used: 2.163 MB
 Metadata Space Total: 2.147 GB
 Metadata Space Available: 2.145 GB
 Thin Pool Minimum Free Space: 10.74 GB
 Udev Sync Supported: true
 Deferred Removal Enabled: false
 Deferred Deletion Enabled: false
 Deferred Deleted Device Count: 0
 Data loop file: /var/lib/docker/devicemapper/devicemapper/data
 WARNING: Usage of loopback devices is strongly discouraged for production use. Use `--storage-opt dm.thinpooldev` to specify a custom block storage device.
 Metadata loop file: /var/lib/docker/devicemapper/devicemapper/metadata
 Library Version: 1.02.74 (2012-03-06)
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins: 
 Volume: local
 Network: bridge host macvlan null overlay
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 4ab9917febca54791c5f071a9d1f404867857fcc
runc version: 54296cf40ad8143b62dbcaa1d90e520a2136ddfe
init version: 949e6fa
Kernel Version: 3.10.23-xxxx-std-ipv6-64
Operating System: Debian GNU/Linux 7 (wheezy)
OSType: linux
Architecture: x86_64
CPUs: 4
Total Memory: 15.58 GiB
Name: ns385050.ip-46-105-124.eu
ID: IKHU:5F2L:CYJL:OWCQ:LVGN:N6NP:SKMM:XAST:THSF:HVKT:NJFN:U5EM
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
WARNING: No kernel memory limit support
WARNING: No cpu cfs quota support
WARNING: No cpu cfs period support
WARNING: No cpu shares support
Experimental: false
Insecure Registries:
 127.0.0.0/8
Live Restore Enabled: false

[noxiouz]

docker version

[on-meetsys]

Docker version 17.03.1-ce, build c6d412e

[alextes]

There seems to be an issue with the flags not having double dashes. Looks like someone's editor decided that '--' is equivalent to a long dash '—'.

docker run -d --env DOCKER_API_VERSION=1.24 --net=host -v /run:/var/run sonm/insonmnia:alpha3 sonmminer --hubaddress=localhost:10002

[on-meetsys]

I've noticed it, and used '--'. I still have the same issue.

docker run -d --env DOCKER_API_VERSION=1.24 --net=host -v /run:/var/run sonm/insonmnia:alpha3 sonmminer —hubaddress=localhost:10002
51b1046bccadd77e90bccf3589397008cee0e6a8ac65f808fec359d677db9e65
docker: Error response from daemon: oci runtime error: container_linux.go:247: starting container process caused "process_linux.go:245: running exec setns process for init caused \"exit status 29\"".

[RiadVargas]

Hey @on-meetsys,
Instead of:
docker run -d --env DOCKER_API_VERSION=1.24 --net=host -v /run:/var/run sonm/insonmnia:alpha3 sonmminer —hubaddress=localhost:10002

You should use
docker run -d --env DOCKER_API_VERSION=1.24 --net=host -v /run:/var/run sonm/insonmnia:alpha3 sonmminer --hubaddress=localhost:10002

I expect it can solve your problem.