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?)
icon14.gif  Re: Docker daemon fails to start on host but succeeds in VZ container [message #52682 is a reply to message #52678] Wed, 07 December 2016 11:46 Go to previous messageGo to previous message
abufrejoval is currently offline  abufrejoval
Messages: 21
Registered: November 2016
Location: Frankfurt
Junior Member
Dead on, nailed it!

On VZ7 "options nf_conntrack ip_conntrack_disable_ve0=1" is in /etc/modprobe.d/vz.conf and the funny thing is I had found that line, 'removed' it and rebooted but that didn't seem to change anything.

Either it defaults to 1, or renaming vz.conf to vz.conf.DISABLED didn't do the job or I botched the reboot.

Setting it to 0 (and rebooting), however, fixed it.

That you soo much!

Any special way to mark this thread as closed?

BTW: Still hoping for news on /proc/driver/nvidia/params or for a hint on where to change that myself (not afraid to compile a kernel, but procfs stuff is all over the place)

Report message to a moderator

[Message index]
 
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:
  

[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Mon Feb 16 02:50:20 GMT 2026

Total time taken to generate the page: 0.28994 seconds
Powered by FUDforum Powered by Virtuozzo Containers