OpenVZ Forum


Home » General » Support » Docker daemon fails to start on host but succeeds in VZ container (iptable 'nat' table missing on host but present in VZ container?)
Re: Docker daemon fails to start on host but succeeds in VZ container [message #52685 is a reply to message #52682] Wed, 07 December 2016 16:32 Go to previous messageGo to previous message
khorenko is currently offline  khorenko
Messages: 533
Registered: January 2006
Location: Moscow, Russia
Senior Member
Tried the same:
# mv /etc/modprobe.d/vz.conf /etc/modprobe.d/vz.conf.DISABLED
# cat /etc/modprobe.d/vz.conf.DISABLED
options vzevent reboot_event=1
#options nf_conntrack ip_conntrack_disable_ve0=0
options nf_conntrack ip_conntrack_disable_ve0=1

reboot

# cat /sys/module/nf_conntrack/parameters/ip_conntrack_disable_ve0
0


So in case you face again that omitting ip_conntrack_disable_ve0=0 makes your node to disable conntracks, please let us know.


If your problem is solved - please, report it!
It's even more important than reporting the problem itself...
 
Read Message
Read Message
Read Message icon14.gif
Read Message
Read Message
Previous Topic: OpenVZ docker version mismatch with CentOS and daemon fails to start
Next Topic: Ploop compact not working - Call FITRIM loop
Goto Forum:
  


Current Time: Sun Oct 26 13:15:44 GMT 2025

Total time taken to generate the page: 0.09691 seconds