<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
    <?xml-stylesheet href="/s/inc/rss.xsl" type="text/xsl"?>
    <rss version="2.0"  xmlns:atom="http://www.w3.org/2005/Atom">
        <channel>
            <title>RSS feed for tag proxmox on Raymii.org</title> 
            <link>https://raymii.org/s/tags/proxmox.xml</link> 
            <description>RSS feed for tag proxmox on Raymii.org</description>
            <atom:link href="https://raymii.org/s/tags/proxmox.xml" rel="self" type="application/rss+xml" />
    
            <item>
                <title>Finally, run Docker containers natively in Proxmox 9.1 (OCI images)</title> 
                <link>https://raymii.org/s/tutorials/Finally_run_Docker_containers_natively_in_Proxmox_9.1.html?utm_medium=rss&amp;utm_source=raymii&amp;utm_campaign=tagrss</link> 
                <guid>https://raymii.org/s/tutorials/Finally_run_Docker_containers_natively_in_Proxmox_9.1.html</guid>
                <description>Proxmox VE is a virtualization platform, like VMWare, but open source, based on Debian. It can run KVM virtual machines and Linux Containers (LXC). I've been using it for over 10 years, the [first article I wrote mentioning it was in 2012](/s/tags/proxmox.html). At home I have a 2 node Proxmox VE cluster consisting of 2 HP EliteDesk Mini machines, both running with 16 GB RAM and both an NVMe and SATA SSD with ZFS on root (256 GB). It's small enough (physically) and is just enough for my homelab needs specs wise. Proxmox VE 9.1 was released [recently](https://www.proxmox.com/en/about/company-details/press-releases/proxmox-virtual-environment-9-1) and this new version is able to run Docker containers / OCI images natively, no more hacks or VM's required to run docker. This post shows you how to run a simple container from a docker image.</description> 
                <pubDate>Thu, 20 Nov 2025 22:34:00 GMT</pubDate>
                <lastBuildDate>Thu, 20 Nov 2025 22:34:00 GMT</lastBuildDate>
            </item>
    
            <item>
                <title>Proxmox VE 7 Corosync QDevice in a Docker container</title> 
                <link>https://raymii.org/s/tutorials/Proxmox_VE_7_Corosync_QDevice_in_Docker.html?utm_medium=rss&amp;utm_source=raymii&amp;utm_campaign=tagrss</link> 
                <guid>https://raymii.org/s/tutorials/Proxmox_VE_7_Corosync_QDevice_in_Docker.html</guid>
                <description>At home I have a 2 node Proxmox VE cluster consisting of 2 HP EliteDesk Mini machines, both running with 16 GB RAM and both an NVMe and SATA SSD with ZFS on root (256 GB). It's small enough (physically) and is just enough for my homelab needs specs wise. Proxmox VE has support for clustering. For a cluster (in any sense of the word), you need at least 3 nodes, otherwise there is no quorum. Corosync, the cluster software used by Proxmox, supports an external Quorum device. This is a small piece of software running on a third node which provides an extra vote for the quorum. In my case I wanted to run this on my NAS, since (physical) space is a premium. The NAS supports Docker, this guide explains how to run the QDevice for Proxmox VE 7 in a Docker container. There is a qdevice Docker image on the Docker hub but that guide does not work for Proxmox VE 7 and requires a lot of manual setup. Using my method involves a lot less steps, since you're basically running an extra debian VPS (a container with systemd and openssh).</description> 
                <pubDate>Sun, 17 Apr 2022 00:00:00 GMT</pubDate>
                <lastBuildDate>Mon, 29 Jan 2024 04:30:00 GMT</lastBuildDate>
            </item>
    
            <item>
                <title>OpenVZ/Proxmox - pre-backup all container dump script</title> 
                <link>https://raymii.org/s/software/OpenVZ_Proxmox_-_pre-backup_all_container_dump_script.html?utm_medium=rss&amp;utm_source=raymii&amp;utm_campaign=tagrss</link> 
                <guid>https://raymii.org/s/software/OpenVZ_Proxmox_-_pre-backup_all_container_dump_script.html</guid>
                <description>This simple script creates a vzdump of all the OpenVZ containers on a machine. It can be used before an actual backup, in my case the actual backup excludes the container path /var/lib/vz/private. This because a dump is easier to backup because it has much less files in it.</description> 
                <pubDate>Sun, 18 Jan 2015 00:00:00 GMT</pubDate>
                <lastBuildDate>Sun, 18 Jan 2015 00:00:00 GMT</lastBuildDate>
            </item>
    
            <item>
                <title>OpenVZ/Proxmox - Container to Template</title> 
                <link>https://raymii.org/s/tutorials/OpenVZ_Proxmox_Container_to_Template.html?utm_medium=rss&amp;utm_source=raymii&amp;utm_campaign=tagrss</link> 
                <guid>https://raymii.org/s/tutorials/OpenVZ_Proxmox_Container_to_Template.html</guid>
                <description>This guide will show you how to convert an OpenVZ (Proxmox) container to a template. You can then use this template on any other OpenVZ (or proxmox) host. This can be used either to migrate containers or to create a kind of master image to deploy new hosts from.</description> 
                <pubDate>Fri, 11 Jul 2014 00:00:00 GMT</pubDate>
                <lastBuildDate>Fri, 11 Jul 2014 00:00:00 GMT</lastBuildDate>
            </item>
    
            <item>
                <title>Proxmox VE - One Public IP</title> 
                <link>https://raymii.org/s/tutorials/Proxmox_VE_One_Public_IP.html?utm_medium=rss&amp;utm_source=raymii&amp;utm_campaign=tagrss</link> 
                <guid>https://raymii.org/s/tutorials/Proxmox_VE_One_Public_IP.html</guid>
                <description>This guide will show you how to set up Proxmox with only one public IP. We will configure an extra interface bridge and make sure VM traffic is NATed. I have a few dedicated servers, some run Proxmox. Most of them however have only a few IP's. Therefore the VM's in proxmox cannot all have a public IP. For most of them that is not a problem. If needed I run a proxy or set up iptables to forward ports to the VM's.</description> 
                <pubDate>Thu, 10 Jul 2014 00:00:00 GMT</pubDate>
                <lastBuildDate>Thu, 10 Jul 2014 00:00:00 GMT</lastBuildDate>
            </item>
    
            <item>
                <title>ProxBash - a bash script to manage Proxmox VE</title> 
                <link>https://raymii.org/s/software/ProxBash.html?utm_medium=rss&amp;utm_source=raymii&amp;utm_campaign=tagrss</link> 
                <guid>https://raymii.org/s/software/ProxBash.html</guid>
                <description>ProxMox VE is a very nice piece of software to setup a VM host very fast, which also is easy manageable via a webinterface. It supports both OpenVZ and KVM. I use it to manage a few VM's to test stuff on and it works really great. However, I'm a command line lover, and I thought it would be nice to be able to 'Manage' Proxmox VE from a bash shell. And I've written a script to do just that. </description> 
                <pubDate>Thu, 28 Jun 2012 00:00:00 GMT</pubDate>
                <lastBuildDate>Thu, 28 Jun 2012 00:00:00 GMT</lastBuildDate>
            </item>
    
        </channel>
    </rss>
    
    