<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>phpVirtualbox on Pjotrs.nl</title>
    <link>https://pjotrs.nl/tags/phpvirtualbox/</link>
    <description>Recent content in phpVirtualbox on Pjotrs.nl</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 19 Nov 2023 20:25:21 +0100</lastBuildDate><atom:link href="https://pjotrs.nl/tags/phpvirtualbox/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Upgrading PhpVirtualbox From 6.x to 7.x on Debian Bullseye, the journey</title>
      <link>https://pjotrs.nl/posts/upgrading-phpvirtualbox-from-6.x-to-7.x/</link>
      <pubDate>Sun, 19 Nov 2023 20:25:21 +0100</pubDate>
      
      <guid>https://pjotrs.nl/posts/upgrading-phpvirtualbox-from-6.x-to-7.x/</guid>
      <description>In my previous blog post I&amp;rsquo;ve described how to install PhpVirtalbox version 6.x however jazzdd released a new version Jenkins. In this post I&amp;rsquo;m describing my journey to update to version 7.x, since the frontend is not compatible with the older version of virtualbox :/.  PhpVirtualbox 7.x is not compatible with 7.0
  Removing the old version of Virtualbox No big surprises here, and if you&amp;rsquo;re trying to follow allong.</description>
    </item>
    
    <item>
      <title>Running (php)Virtualbox on a Readonly Root System</title>
      <link>https://pjotrs.nl/posts/running-phpvirtualbox-on-a-readonly-root-system/</link>
      <pubDate>Mon, 02 Jan 2023 16:29:55 +0100</pubDate>
      
      <guid>https://pjotrs.nl/posts/running-phpvirtualbox-on-a-readonly-root-system/</guid>
      <description>Since I like to run servers from USB sticks and store the server data on harddisks. It is wise to make the root-file system read-only, to extend the life of a USB-stick. However, some programs require extra configuration to do this, since I could not find a post to do this with VirtualBox I&amp;rsquo;m making this one.
Figuring out which files need to be writeable for Virtualbox We can use strace, to find the calls an application makes to the OS, (If you&amp;rsquo;re using Windows, process monitor can do similar, but still different things (including registry access) ).</description>
    </item>
    
    <item>
      <title>Running PhpVirtualbox Inside of Kubernetes</title>
      <link>https://pjotrs.nl/posts/running-phpvirtualbox-inside-of-kubernetes/</link>
      <pubDate>Mon, 07 Nov 2022 14:22:15 +0100</pubDate>
      
      <guid>https://pjotrs.nl/posts/running-phpvirtualbox-inside-of-kubernetes/</guid>
      <description>This guide assumes you&amp;rsquo;re running Debian (10), this guide will use Virtualbox 5.2. If you&amp;rsquo;re running version 6, of Virtualbox, please use the VBOX6.x tag of the jazzdd/phpvirtualbox Docker image.
Look here for debian 11: https://linuxopsys.com/topics/install-virtualbox-on-debian
Install Virtualbox on the host As root run the following commands.
apt install virtualbox-5.2 Edit or create _/etc/default/virtualbox _and make sure you set the username and host settings (update it with the information for your setup) e.</description>
    </item>
    
  </channel>
</rss>
