New answers tagged


So after a little bit more research I've determined why this is happening. I'm using the default Ubuntu and Debian templates to create the containers and their networking is set up so as to use DHCP to ask for a IP from the the router. So initially the static IP is set using the lxc.container.config and then when the container starts it queries the router (...


Make sure netctl and dhcpcd is installed inside the container (pacman -Q netctl dhcpcd) then run the following in the container: cat > /etc/netctl/eth0 Connection=ethernet IP=dhcp Interface=eth0 Press CTRL-D to write the file. Then enable the profile by running: netctl enable eth0 Finally restart the container and you should have a DHCP assigned IP ...


lxc-attach allows you to run a command in a container without logging in. lxc-attach -n container-name -- <command> So I guess you need to run: lxc-attach -n container-name -- sudo tc qdisc add dev eth0 root netem delay 128ms the output of the command, if any, is redirected to your standard outputs.


Setting up a bridge is extra work. Someone has to do this work. Since some containers should be bridged and others shouldn't be bridged, container utilities don't systematically set up a bridge. It's very common for a container not to be bridged. The point of a container is to isolate the container from the rest of the world. This often means that the ...

Top 50 recent answers are included