Comment # 6 on bug 1036356 from Alexandre Vicenzi

(In reply to Jordi Massaguer from comment #4)
> the runc issue is more concerning.
> 
> Can you give us the output of:
> 
> rpm -qa | grep docker

docker-libnetwork-0.0.0+git20161019.0f53435-1.1.x86_64
docker-compose-1.8.1-1.1.noarch
docker-bash-completion-1.13.0-2.1.noarch
docker-image-migrator-1.0.2-2.4.x86_64
docker-zsh-completion-1.13.0-2.1.noarch
python-dockerpty-0.4.1-1.2.noarch
docker-1.13.0-2.1.x86_64
python-docker-pycreds-0.2.1-3.1.noarch
python-docker-py-1.10.6-1.1.noarch

> rpm -qa | grep runc

runc-0.1.1+gitr2942_2f7393a-2.1.x86_64

> 
> ls -l /usr/bin/docker-runc

lrwxrwxrwx 1 root root 12 abr 17 06:04 /usr/bin/docker-runc -> ../sbin/runc

> ls -l /usr/sbin/runc

-rwxr-xr-x 1 root root 4996288 abr 17 06:04 /usr/sbin/runc

> 
> runc --version

runc version spec: 1.0.0-rc2-dev

> 
> I see it is also a warning. Is this causing you some real issue? I mean, are
> you able to run your docker images even the warning?

As far as I know everything is working. Didn't had any problem with docker.