0

nova-docker on mitaka unable to boot instances

nova-docker

asked 2016-06-01 16:20:01 -0600

ykuo
1 ●2 ●4 ●3

Configured compute node with nova-docker with either the master branch or stable/mitaka branch, and when trying to boot docker instances, it does not boot up.

nova list shows the status is ACTIVE with assigned IP address with provider network. nova show <instance-id> does not show any error.

But on the compute node, docker ps does not show the docker image running.

vnc console shows mesage: no bootable device

and I also noticed that in the liberty release, the hypervisor type for compute node is 'docker' but with mitaka release, it is set us 'QEMU'

Any help is appreciated.

edit retag flag offensive close merge delete

Comments

docker ps -a shows the container? vnc won't work because probably the container don't have any vnc connection method

Eduardo Gonzalez ( 2016-06-02 02:07:01 -0600 )edit

1.If it's possible post Dockerfile been used to build docker image uploaded to Glance.
2.Test ubuntu/rastasheep or tutum/tomcat to be loaded as Nova-Docker instances
The last images have been tested hundreds of times ( positive ) with Nova-Docker (Mitaka,Liberty,Kilo )

dbaxps ( 2016-06-02 04:47:31 -0600 )edit

docker ps -a does not show the container on compute host

tried to boot tutum/tomcat, same issue.

ykuo ( 2016-06-02 12:46:11 -0600 )edit

It's a fair Nova-Docker (Mitaka,Liberty) works fine. You made some mistakes during driver installation
See for instance https://www.linux.com/blog/java-serve...

dbaxps ( 2016-06-02 13:25:08 -0600 )edit

I followed instructions from http://egonzalez.org/nova-docker-driver/ the same instruction works for liberty, but not for mitaka.

ykuo ( 2016-06-02 13:46:53 -0600 )edit

see more comments

1 answer

Sort by » oldest newest most voted

0

answered 2016-06-02 14:29:13 -0600

ykuo
1 ●2 ●4 ●3

rootwrap needs to be setup on all hosts (controller + all compute hosts)

vi /etc/nova/rootwrap.d/docker.filters

[Filters]
# nova/virt/docker/driver.py: 'ln', '-sf', '/var/run/netns/.*'
ln: CommandFilter, /bin/ln, root

It was not setup on controller which caused the issue

edit flag offensive delete link

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2016-06-01 16:20:01 -0600

Seen: 583 times

Last updated: Jun 02 '16

Related questions