Home » Proxmox
Proxmox / LXC – Running docker inside a container
In relation to Debian / Proxmox – Install Docker with Rancher and DockerUI webgui on a Debian / Proxmox Server
I thought that it actually may make more sense to run Rancher and my docker inside an LXC container rather than on the initial host itself.
I went back to utilize an old Machine with Proxmox for containers but also wanted to have a platform to play with Docker. So I though pimping the Promox server is the best solution.
The Steps are easy to get docker running but since Proxmox offers the best GUI for lxc I needed something similar for the docker containers.
Note: This DOES NOT add Docker into the Proxmox GUI itself. I’m adding a separate web page for docker running in a container by itself.
Update 02.03.2015: added (modified) Centos / Redhat: A successor to compcache is zram which is fully integrated in the Linux kernel since 126.96.36.199 and uses lzo compression. The idea behind it is to create swap devices made of chunks of the ram and to compress those chunks on the fly to increase the available space used and ideally reduce the need of swapping to slow disks. It uses a small extra amount of the CPU, however, the reduced i/o usage should more than make up for this. This is primarily interesting for a small scaled VPS, Netbooks or low memory devices. Also virtualisation hosts should benefit of compressed memory. Unfortunatly the zram-config script is currently not part of the Debian and Centos distributions. I will run some further tests and update here. In Ubuntu, from 12.04 onwards, the install script is included and it takes only a minute to setup zram. How to […]
Doing some cleanup and had to rename a nodename of an existing standalone Proxmox Server. Found that it wasn’t too straight forward because it detected the old nodename and placed the vz underneath it. So here is a simple way to rename the Proxmox Node. Firstly the normal steps: vi /etc/hosts vi /etc/hostname Replace the entries with your intended hostname. You will now need to restart pve in order to create the new hostname in the system. service pve-cluster restart This should now create a new host entry in Proxmox and a new folder under /etc/pve/nodes/[newhostname] You now need to copy your old openvz data from the old folder to the new. mv /etc/pve/nodes/[oldhostname]/openvz/* /etc/pve/nodes/[oldhostname]/openvz/ Example: mv /etc/pve/nodes/proxmox-portable/openvz/* /etc/pve/nodes/proxmox-Xen/openvz/ I would advise to restart the Proxmox host in order to finish the renaming. Related posts: Linux: Install Proxmox Virtual Environment on Debian 6.0 Squeeze Distro (Kanopix) Debian / Kanotix / […]
Just found this on the Proxmox Wiki https://pve.proxmox.com/wiki/Performance_Tweaks#VZdump stating that the default value for vzdump is limited to 10000 Kbps (10 Mbps). This might explain even my misunderstanding why backups to my NAS are pretty “slow” sudo vi /etc/vzdump.conf showed that the original line in Proxmox 3.2 is #bwlimit: KBPS which I changed for now without notable issues to bwlimit: 40000 However James Coyle mentioned running into another issue with a too high value on undersized servers. http://www.jamescoyle.net/how-to/290-limit-backup-io-bandwidth You should keep that in mind if you are about to bring your server down while running vzdump backups. Related posts: Proxmox: Getting some performance data from a Proxmox server Proxmox: OpenVZ (OVZ) and Turnkey Appliances root password Linux: Install Proxmox Virtual Environment on Debian 6.0 Squeeze Distro (Kanopix) Debian 7.0 Wheezy / Proxmox 3.x: Install ZFS Native Proxmox: Rename a standalone node (hostname) Debian / Proxmox – Install Docker with Rancher and DockerUI webgui on […]
For the Records, in order to get performance data from a proxmox server you can use: pveperf root@proxmox1:~# pveperf CPU BOGOMIPS: 21281.44 REGEX/SECOND: 1039338 HD SIZE: 28.05 GB (/dev/mapper/pve-root) BUFFERED READS: 11.60 MB/sec AVERAGE SEEK TIME: 26.35 ms FSYNCS/SECOND: 28.37 DNS EXT: 70.92 ms DNS INT: 64.58 ms (Cloud7-ITConsult.com) Related posts: Proxmox : vzdump performance optimization Linux: Install Proxmox Virtual Environment on Debian 6.0 Squeeze Distro (Kanopix) Debian / Kanotix / Proxmox: Install ZFS Native Debian 7.0 Wheezy / Proxmox 3.x: Install ZFS Native Proxmox: OpenVZ (OVZ) and Turnkey Appliances root password Proxmox: Rename a standalone node (hostname)
This is a bizarre one. Either I wasn’t able to search for the right pages and posts or it’s simply poorly documented. Particularly under Proxmox (I will need to bump up my opennode to check on that one). One of the best features there, are the turnkey templates. Seriously, a few clicks and you have loads of great appliances up and running powered by turnkey templates. Sadly they are all Debian based but thats another story. But deploying and get it running such a template kind of was not straight forward. This applies to a “new” turnkey 13.1 template (I tried the nginx) You download the templates through the gui -> create a new CT -> give it your root password -> select the template -> install -> boot ->ssh to it (or maybe even try the Proxmox console) -> fail. At least in 3 cases on my systems I […]
In relation to the outdated post http://www.solaris-cookbook.eu/linux/debian-kanotix-proxmox-install-zfs-native/ Things have become much easier now How to install ZFS native on Debian 7 or Proxmox 3.x 1) become root sudo su – 2) Install ZFS wget http://archive.zfsonlinux.org/debian/pool/main/z/zfsonlinux/zfsonlinux_3%7Ewheezy_all.deb dpkg -i zfsonlinux_3~wheezy_all.deb apt-get update apt-get install debian-zfs kernel upgrade After updating the Kernel you most likely have to do the following steps: make sure you have the headers installed (proxmox example) aptitude install pve-headers-$(uname -r) (it will pick the current running kernel version. If you just updated the kernel you better reboot first.) ln -s /lib/modules/$(uname -r)/build /lib/modules/$(uname -r)/source aptitude reinstall spl-dkms zfs-dkms That should cover you on a kernel update Related posts: Debian / Kanotix / Proxmox: Install ZFS Native Linux: Install Proxmox Virtual Environment on Debian 6.0 Squeeze Distro (Kanopix) ZFS: Fun with ZFS – is compression and deduplication useful for my data and how much memory do I need for zfs dedup? […]
Situation: I used to run a Proxmox 2.x on Debian 6.0 Dev box. I somehow sufficiently manage to corrupt the whole OS and config. I had snapshots and backups to go back but I decided to go the big thing and install fresh Proxmox 3.x on Debian 7.0 to a newer and faster hard-drive. If you ever decide go this path, then please consider the following: make backups of the following directories /etc /var/lib/pve-cluster/ Name the host the same way as it was on the old installation. (I tried a different hostname and it didn’t work) Use the same IP Address and it was on the old host. (I tried a different IP and it didn’t work) So I rebuild Proxmox 3.x from scratch and it was as expected blank. I had my data (images, templates, kvm and openVZ data) on a ZFS disk and remounted that one to the […]
Based on http://pve.proxmox.com/wiki/Package_repositories To Enable the PVE testing (Proxmox testing channel) do the following: vi /etc/apt/sources.list Insert # PVE packages provided by proxmox.com deb http://download.proxmox.com/debian squeeze pvetest Then update the system by using: apt-get update;apt-get dist-upgrade Related posts: Linux: Install Proxmox Virtual Environment on Debian 6.0 Squeeze Distro (Kanopix) Debian / Kanotix / Proxmox: Install ZFS Native Debian 7.0 Wheezy / Proxmox 3.x: Install ZFS Native Proxmox: Getting some performance data from a Proxmox server Proxmox: OpenVZ (OVZ) and Turnkey Appliances root password Proxmox: Rename a standalone node (hostname)