Hi all,
Seems that no syslog daemon is included in the default Debian template no ?
Am I dreaming ?
Marc
___
lxc-users mailing list
lxc-users@lists.linuxcontainers.org
http://lists.linuxcontainers.org/listinfo/lxc-users
Is there any additional task to perform?
It should be ok from my point of view !
You may also copy the conffiles.. (the whole container directory.. not
just the rootfs..)
___
lxc-users mailing list
lxc-users@lists.linuxcontainers.org
http://lists.
Because host networking is very distro-dependent, we cannot do a lot
of things in upstream lxc. However we're starting to ship things
under config/, so if we can figure out how to do this for the most
common distros, that'd be nice.
If you blog a concise explanation/tutorial of the minimal steps
Hi,
thanks a lot for your answers.
well ... nothing outside the server should even know about the
container's MAC address. Because if the network setup is the same as
mine, then the provider's router would route all traffic for the
container thru main server's IP. In other words, the provider's r
host to respond to those arp queries ?
I found some post on how it's done with openvz venet :
http://forum.openvz.org/index.php?t=msg&goto=35611&;
Any clue ?
Le 21/05/2014 16:41, Fajar A. Nugraha a écrit :
On Wed, May 21, 2014 at 9:19 PM, Marc MAURICE
wrote:
I finally made it w
I finally made it work with veth mode, and a bridge on the host, but it's
frustrating.
And I have to manually generate and allow all mac adresses (required by my
server hoster).
I'd just comment on this one first.
What is your hoster like? Is it like serverloft where you can buy
additional IP
Hello all,
I'm trying to setup the following simple config :
* a lxc host (single network interface, single public IP1)
* a lxc container (single public IP2)
I would like to achieve the same as OpenVZ venet, where all containers
have dedicated IPs, but are sharing the MAC address of the host.
