<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>Hi,</div><div><br></div><div>I don't think that this mailinglist is the correct place for questions about a lxc problem, that has nothing to do with ovz.</div><div><br></div><div>However, I also tried what happens when converting from ovz to lxc (Proxmox). From my experience I can confirm that it can cause serious problems when converting a multi IP ovz container to lxc. I was not able to do this with success. I had to split up services to multiple lxc containers with only one IPv4/6 each. No other option worked for me and I gave up finding the reason.</div><div><br><br>Regards<br><div> Volker</div><div><br></div></div><div><div><div><br></div></div>Am 20.07.2016 um 11:13 schrieb Christian Blaich <<a href="mailto:christian@blaich.eu">christian@blaich.eu</a>>:<br><br></div><blockquote type="cite"><div>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style>
<div dir="ltr">Hey,<br><br>i'm doing a few tests with migrating ovz containers to lxc. Learning about advantages and disadvantages of both.<br>Here are the instructions that i use to convert the containers: <a href="https://pve.proxmox.com/wiki/Convert_OpenVZ_to_LXC" target="_blank">https://pve.proxmox.com/wiki/Convert_OpenVZ_to_LXC</a><br>The main point that i struggle is to switch from venets to the eths of lxc.<br><br>Running the container with one eth0 and one ip works perfect. But with a second interface eth1 and a second ip there is some routing problem. The second ip is not pingable from outside.<br>I'm using precreated images from here <cite class="_Rm"><a href="https://wiki.openvz.org/Download/template/precreated" target="_blank">https://wiki.openvz.org/Download/template/precreated</a> (Ubuntu 12.04 and Ubuntu 14.04)<br><br>interfaces inside the container:<br></cite>auto eth0<br>iface eth0 inet static<br><pre> address xx.xx.xx.xx<br> netmask 255.255.255.255<br># --- BEGIN PVE ---<br> post-up ip route add xx.xx.xx.254 dev eth0<br> post-up ip route add default via xx.xx.xx.254 dev eth0<br> pre-down ip route del default via xx.xx.xx.254 dev eth0<br> pre-down ip route del xx.xx.xx.254 dev eth0<br># --- END PVE ---<br>auto eth1 <br>iface eth1 inet static<br> address xx.xx.xx.xx<br> netmask 255.255.255.255<br> </pre>Original templates from lxc don't have that problem. My question - is there any setting inside the container template that forbids the routing to eth1?<br><br>Thank you, chris<br> </div>
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>Users mailing list</span><br><span><a href="mailto:Users@openvz.org">Users@openvz.org</a></span><br><span><a href="https://lists.openvz.org/mailman/listinfo/users">https://lists.openvz.org/mailman/listinfo/users</a></span><br></div></blockquote></body></html>