-
Notifications
You must be signed in to change notification settings - Fork 129
failed to start a container with docker #656
Comments
It because the new version of docker depends on the format of the output of the |
Fixes: hyperhq#656 Signed-off-by: Lai Jiangshan <[email protected]>
still hava trouble with staring a container if use docker run -it busybox /bin/sh will have a error: the full journalctl log Dec 22 17:25:10 compute kernel: XFS (dm-1): Mounting V5 Filesystem |
I can't find the relevant log from it. |
still not working, i have some infos in /var/log/hyper, are these infos useful? ==> runv.INFO <== |
there are several log files for one container. It seems the error message is not in runv.INFO. Cloud you also post the other files, please. |
[root@compute hyper]# cat runv.WARNING [root@compute hyper]# cat runv.ERROR |
Is there any progress? |
I can't find anything from these files. |
hello, could you please post all the logs? |
that's all log in "/var/log/hyper/". any more info on where i can find? |
Same issue here with Only found some log from
|
got the same error while using runv:1.0.0 with docker-ce-18.03 in centos 7: time="2018-04-25T23:47:46.720831433+08:00" level=warning msg="failed to retrieve runv version: unknown output format: runv version 1.0.0\nspec: 1.0.1\n" |
@telala could you try docker 17.12 or 17.06 instead? docker will change some configurations randomly, which is not standardized yet, as a result, it may break runtimes other than runc. |
I used to use docker ce 17.09 and it is ok with runv. |
@bergwolf are you working on investigating this? |
I think it's the same as #677. docker has changed its network configuration since certain release. I need some time to investigate what was changed though. moby stopped tagging releases after v17.03.2-ce, so it's hard to tell from moby's code change. |
Fixes: hyperhq#656 Signed-off-by: Lai Jiangshan <[email protected]>
follow the doc "Run it with docker"
when i start a container, the container will fail.
errorlog:
compute dockerd[25828]: time="2017-12-22T11:49:56.871309975+08:00" level=warning msg="failed to retrieve /usr/local/bin/runv version: unknown output format: runv version 1.0.0, commit: \n"
my docker version info
Containers: 9
Running: 0
Paused: 0
Stopped: 9
Images: 42
Server Version: 17.12.0-ce-rc3
Storage Driver: devicemapper
Pool Name: docker-8:3-269506593-pool
Pool Blocksize: 65.54kB
Base Device Size: 10.74GB
Backing Filesystem: xfs
Udev Sync Supported: true
Data file: /dev/loop0
Metadata file: /dev/loop1
Data loop file: /var/lib/docker/devicemapper/devicemapper/data
Metadata loop file: /var/lib/docker/devicemapper/devicemapper/metadata
Data Space Used: 4.419GB
Data Space Total: 107.4GB
Data Space Available: 103GB
Metadata Space Used: 6.058MB
Metadata Space Total: 2.147GB
Metadata Space Available: 2.141GB
Thin Pool Minimum Free Space: 10.74GB
Deferred Removal Enabled: true
Deferred Deletion Enabled: true
Deferred Deleted Device Count: 0
Library Version: 1.02.140-RHEL7 (2017-05-03)
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
Volume: local
Network: bridge host kuryr macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file logentries splunk syslog
Swarm: inactive
Runtimes: runc runv
Default Runtime: runv
The text was updated successfully, but these errors were encountered: