#solum

Author: Ed Cranford <ed.cranford@rackspace.com>;

Date: Thu Jun 25 14:35:29 2015 -0500

Add kernel-extras to installed packages

wasn't that the commit which enables aufs?

that is available in my Vagrant setup

try start docker daemon with ----storage-driver=aufs manually

ok

getting "invalid option —storage-driver=aufs"

do you remember the exact command?

sudo docker -s aufs

james_li: thanks.. this worked for me: sudo docker -d --storage-opt aufs

ok then try sudo docker --debug

you mean try running the daemon with debug flag?

or modify /etc/default/docker: DOCKER_OPTS="--debug -s aufs"

james_li: https://gist.github.com/devdattakulkarni/619f3d...

then you can do sudo service docker restart

"Running modprobe bridge nf_nat failed with message: , error: exit status 1"

kernel module probelm

you mean the bridge nf_nat failed error is due to kernel module problem?

I guess you VM kernel has problems, if I were you, I would just create another brand new VM

james_li: ok, let me try that

james_li: can you verify that last commit in here https://github.com/rackerlabs/vagrant-solum-dev is actually the way to install required kernel packages for running aufs?

our team meeting will begin in 5 minutes at 2100 UTC in #openstack-meeting-alt

devkulkarni: looks yes

james_li: ok

I will rebuild my VM

devkulkarni: more CLI fun includes the -E flag which deliberately doesn't swallow the stacktrace

datsun180b: nice!

i make heavy use of that

james_li: have got a fresh vm

lets see if the docker daemon with aufs option starts up or not

yeah

randallburt: so the main point that james_li wanted to suggest was related to the api changes in your spec

devkulkarni: k. is the meeting done?

randallburt: yes — we just finished

few minutes back

randallburt: we suggested a better name for api change

devkulkarni: perfect timing :D

randallburt: ha ha

james_li: k. seems like the best place for that feedback would be in a review

yes

devkulkarni: i missed the meeting!!! i'm so sorry!!!

i blame lack of sleep

dimtruck: no worries

you need to take some rest actually

check the meeting notes

we did not discuss the ops guide

so you did not miss much

james_li: still same error. I am reverting back ed's patch to vagrant and going to check if that makes a difference

jvrbanac: did the barbican.pid file also change? http://logs.openstack.org/33/206633/1/check/gat...

ok

devkulkarni, I don't think the barbican.pid changed. You might check with someone in the barbican channel

jvrbanac: ok

james_li: ping