search

turnkeylinux / tracker

TurnKey Linux Tracker
https://www.turnkeylinux.org
70 stars 16 forks source link

when creating a container for openvz - ip address for venet0:0 is not detected correctly - finds 127.0.0.2 #700

Closed fiveways closed 4 years ago

fiveways commented 8 years ago

Hi Team, when creating a container for openvz - ip address for venet0:0 is not detected correctly - finds 127.0.0.2

Just started playing with tlk templates with openvz and noticed some templates believe the ip address of the container is 127.0.0.2

Happy for the templates to use the first ip on venet0:0, happy to do testing and provide patches, just not sure where to start.

a3s7p commented 8 years ago

Hi,

Could you please provide some details about your environment?

I would like to know which OS you are running as the OpenVZ host, the version of vzctl and network configuration (bridged or routed). Please also copy&paste the output of those commands executed on the affected VM:

cat /etc/hosts
ifconfig -a
JedMeister commented 8 years ago

As the name suggests, our current "Proxmox" build is optimised for ProxmoxVE (which uses LXC as of v4.0). However I did test them on Proxmox v3.4 (which uses OVZ) and they worked OOTB. Having said that, ideally if we can better support vanilla OVZ without compromising support for LXC/Proxmox support then we should do it. If you can answer @qrntz's questions then we may be able to do that better, or at least make it work a little nicer (i.e. document a workaround, etc).

JedMeister commented 4 years ago

I'm going to close this now. OpenVZ is dead and we've been unable to reproduce this issue on LXC.