well this is more a question on setting up a revers proxy and not really related to ProxMox, VM or DietPi
Thanks a lot for this guide! Good work
Have you ever tried resizing a attached hard disk in proxmox?
I’m just trying to accomplish this, on the proxmox side it’s not a problem, but i can’t get it to work inside DietPi.
Can’t even resize the drive with reformating it inside DietPi, which obviously wouldn’t be very helpful anyway, but still… ^^
Is it even possible…?!
I installed DietPi as a VM on ProxMox too. That was pretty easy.
But I wonder how I can customize the installation beforehand. For the Raspberry Pi I could change the dietpi.txt file. But how do I do that on the ISO??
thanks for this guide, just switched from ESXi to Proxmox and this has got me up and running really quick - thanks for taking the time to put it together.
Btw, using the default SeaBIOS does not work with the BIOS image? I’m thinking about providing a Proxmox image, so that it is also seen internally as VM and not as native PC and has some unnecessary packages less (WiFi tools and firmware, minimal initramfs etc).
Another thing about the Clonezilla selection: Whether you select VGA or KVM or something else doesn’t matter for the final OS but only for the install procedure. Since this is only the whiptail we may remove that selection entirely and preselect the most compatible one instead. Also using one of the in-RAM choices seema to not work (on my last tests).
That would be awesome
I would also be pleased !
maybe you could do it like here ?
https://github.com/ej52/proxmox-scripts/blob/main/lxc/nginx-proxy-manager/README.md
I use this because Nginx Proxy Manager under Docker always refuses to work after some time.
As a whole VM, Dietpi unfortunately consumes too much of my little space. There are a few things that should run in their own container.
I’ve tried this guide on Proxmox 7.1, but fails everytime, changed all settings. No luck
After many tries I got it working…
The steps I took:
I Installed NetDebian Image, all standard settings
Upped memory and started install
I dont need a GUI, just standard system utilities & openSSH server
You have to edit SSH to use Putty
In the proxmox console enter nano /etc/ssh/sshd_config
find PermitRootLogin and remove the #
change PermitRootLogin prohibit-password to PermitRootLogin yes
Save with CTRL X, Y,enter
restart SSH with /etc/init.d/ssh restart
get IP with ip a
Use Putty to login
After login
enter apt update
enter apt install -y curl ca-certificates systemd-sysv
enter bash -c “$(curl -sSfL ‘https://raw.githubusercontent.com/MichaIng/DietPi/master/PREP_SYSTEM_FOR_DIETPI.sh’)”
select master image
enter a name
enter a pre-image name → debian
select nr. 20 - x86_64 Virtual Machine
choose Wifi if you need it
choose Bullseye
sit back and relax.
finished? then reboot
Done, DietPi on Proxmox
please excuse my asking:
you have installed it as VM and not as LXC container ?
You’re right - it really doesn’t work with the current image. But with the one from Buster it does:
DietPi_NativePC-BIOS-x86_64-Buster_Installer
You just have to update everything…
While I’m here:
@MichaIng
Where can I download older versions ?
I have already searched for it
We don’t offer older images by purpose. There is nothing like an archive.
Instead of building images with outdated Debian versions, which will cause you issues and us additional support efforts in the mid/long term, probably you guys want to help debugging why it doesn’t work with the current Bullseye image? E.g. providing error messages, details what/where exactly it “doesn’t work” or so? Just an idea .
You are right.
I should have posted that - sorry
I promise to do better
the problem with Proxmox (v.6.4) is, that the bullseye version doesn’t give an error message and simply aborts the hard disk scan. dietpi is my absolute favourite, but it couldn’t be reinstalled. luckily I still had the buster version and it ran through. then update everything again and I’m back with you.
With the upcoming DietPi v8.2 we will have
- a generated qcow2 image (https://dietpi.com/downloads/images/DietPi_Proxmox-x86_64-Bullseye.7z)
- an installation guide will be available at https://dietpi.com/docs/install/ with an own Proxmox tab
In the past we focused a bit on “Virtual Machinering” and added VM images for the desktop virtualization products Parallels Desktop (macOS), VMware Fusion (macOS) and UTM (macOS). Before we already coped VMware, VirtualBox and Hyper-V.
Also for virtualisation appliance servers like VMware vSphere (ESXi Hypervisor) as well as Proxmox PVE we spend some time.
We hope that the images and descriptions help to use virtualization environments in an easy way.
The descriptions referenced in the former post replies helped a lot to work on these issues.
I think it’s worth to mention that it is recommended to install dbus …
I installed several instances of DietPi on a Proxmox server and had the problem, that Proxmox was not able to freeze / stop / suspend the VMs for backup or rebooting.
Even with installed guest Agent. It turns out, that the dbus package was missing for communicating between host and the VMs.
we will have a look if it could become part of the default ProxMox image
MichaIng
FYI
We recognised this, basically dbus is required for ACPI events, which are used to trigger shutdowns/reboots etc from Proxmox and any other virtualizer. Hence it may make sense indeed to enable it at least for Proxmox and ESXi images where you often want to control many VMs without accessing their console/SSH. For qemu-guest-agent to work, for more control, additionally systemd-logind and libpam-systemd are required. Since we currently use a single VM image to derive all images and appliances for the different virtualizers, we’ll see how to achieve this best. There is a dietpi.txt setting to enable systemd-logind during first run setup, which can be set manually for individual appliances, but installing APT packages into an image after DietPi-PREP has finished, is more complicated. Probably we need to add another settings for dbus only so that ACPI can be enabled without the overhead of systemd-logind, i.e. a finer grained setup option for individual applicances.
Hi
I’m experimenting with Proxmox and have it all working. Followed the guide and imported the image as above.
The hard disk is 8GB. How can I expand it’s default size?
Thx in advance
question raised as additional post https://dietpi.com/forum/t/resizing-hd-after-installing-the-proxmox-package/6462/1
Has anyone got it working in non privileged container?
I do not see why Kodi, o!mpd and many more software packages would need a privileged container, besides the VM needs more resources.