It is a custom script which sets various iptables settings.
as for lxc-connect, this was a typo and was ment to be lxc-console ;-)
I will try the pct command, we only tried to connect via the web interface which yielded the following error when the firewall script was enabled :
timed out...
Hello,
yesterday we migrated a lxc container from an ubuntu lxc server and despite the fact that it started fine and everything seemed to work ok we were not able to access the console via any proxmox methods.
Eventually we disabled the firewall inside the ct via file access to the ct content...
I had the same problem using older hardware that would not recognize the UEFI data on the USB (thumb) drive. After a bios update and "reset to factory defaults" of the bios it all worked fine.
I agree, the only platforms that are supported are the complete hypervisors vmware and XEN and the Libvirt system of SLES 12 (but that's a pain by itself). Unfortunately the NetIQ software we use will only run on SLES so we are stuck to SLES in stead of OpenSUSE.
We've run the software in LXC...
A little update with final tweaks for SLES12SP1 which uses a different set of patterns
mkdir /SLES12SP1
mkdir /SLES12SP1/etc
cp -a /etc/zypp/ /SLES12SP1/etc/zypp
ln -s /SLES12SP1/etc/product.d/SLES.prod /SLES12SP1/etc/product.d/baseproduct
zypper --root /SLES12SP1 ref
zypper --root /SLES12SP1...
Since i looked everywhere for this and couldn't find it anywhere i had to figure it out by some very old documentation and bits and pieces from everywhere. I thought i should share it here to contribute to using SLES 12 as a CT instead of the full blown VM.
These steps should be done on a...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.