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 #52686 is a reply to message #52685] Wed, 07 December 2016 20:22 Go to previous message
abufrejoval is currently offline  abufrejoval
Messages: 21
Registered: November 2016
Location: Frankfurt
Junior Member
Well it's official now, I am sloppy!

I repeated the procdure on my system and it behaves as you describe: Unless specifically disabled for VE0 connection tracking will be enabled also on the host.

After careful examination I cannot find evidence on me rebooting (at least not via the command line) after renaming vz.conf to vz.conf.DISABLED (no time stamps on shell history, no auditing enabled).

I however immediately rebooted after doing the reverse operation.

I knew I'd have to reboot for those changes to be effective, but evidently I did get distracted after doing the right thing first...

Thank you for taking quality seriously and sorry for making you worry in vain! Embarassed

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: Thu Apr 09 13:57:07 GMT 2026

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