Skip to content
This repository has been archived by the owner on Feb 8, 2021. It is now read-only.

Run runv with docker create busybox container failed #677

Open
ZhangSenter opened this issue Apr 24, 2018 · 2 comments
Open

Run runv with docker create busybox container failed #677

ZhangSenter opened this issue Apr 24, 2018 · 2 comments

Comments

@ZhangSenter
Copy link

ENV:
ubuntu16.04.2 64bit
go version go1.10.1 linux/amd64
runv version 1.0.0
Docker version 18.03.0-ce

STEP:

  1. according to the https://github.com/hyperhq/runv/tree/master instructions.
  2. Some steps.
  3. runv --kernel /var/lib/hyper/kernel --initrd /var/lib/hyper/hyper-initrd.img run mycontainer and it was successful, info as follow:
    root@node-dev9:~# runv list
    ID PID STATUS BUNDLE CREATED OWNER
    mycontainer 79976 running /containerbundle 2018-04-24T09:54:03+08:00 root
  4. docker run --rm -it busybox and it was failed, info as follow:
    root@node-dev9:~# docker run --rm -it busybox
    set winsize failed, rpc error: code = Unavailable desc = all SubConns are in TransientFailure

Does it not support ubuntu16.04? Or something else?

@bergwolf
Copy link
Member

@ZhangSenter Thanks for reporting! I can confirm the error in my local setup. Looks like something has changed in docker's network configuration.

I0424 13:49:07.180841   22405 network.go:433] get interface {47 48 172.17.0.2/16 02:42:ac:11:00:02 eth0 1500}
I0424 13:49:07.355826   22405 network.go:444] got mirredPairs: [{47 49}]
E0424 13:49:07.363465   22405 network.go:464] no such file or directory

Need to take a closer look at it.

@qifcheng
Copy link

It seems that it's the docker version problem, I meet the same issue when I use docker-ce 17.03, it works fine after I upgrade the docker version to 17.06 as offical doc said.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants