New answers tagged lxc
Remember how I said: The system uses lxc containers for compartmentalisation, but that shouldn't matter here. Well, turns out it did matter. Or rather, the cgroups at the heart of lxc matter. The host machine only sees reboots for kernel upgrades. So, what were the last kernels used? 3.19, replaced by 4.0.5 2 months ago and yesterday with 4.1.3. And ...
I, personally prefer a different approach. Given that the OS part of the containers is relatively small (max. 2GB a debian jessie server with plenty of services running, about 3Gb a working ubuntu image with remote desktop), I leave the OS reside in /var/lib/lxc and use a separate partition for the container's data. This is simply accomplished modifing the ...
In your command ping -c 1 -t 1 192.168.236.2 You are specifying that the packets are to be send with a TTL of 1. This means they will traverse at most one network hop before producing an error. In your network configuration your CentOS 6.3 node is not directly connected to the NAT you are trying to reach. The CentOS 6.5 node is between the two. When you ...
yaegashi's VMWare comment pushed me in the right direction. I had to enable promiscuous mode on the Virtual Machine Port Group on the esxi host. Otherwise, the virtual switch won't allow traffic through the port with a mac address different from the the virtual adapter's mac address.
In /var/lib/lxc/Solr4StandAlone/config add a line reading: lxc.mount.entry = /mnt/ssd/solr_data /var/lib/lxc/webserver/Solr4StandAlone/rootfs/data none bind 0 0 Then lxc-stop stop your container and lxc-start your container again. That is all that is needed. ref: reference link
Top 50 recent answers are included