Hi,
I tried to find a solution looking at dual boots in this forum and on the internet but I didn’t find any way to solve my issue:
I have a RaspPi 4 with Raspberry Pi OS 64bits 4GB installed since years on a 2TB HDD (it directly boots on the HDD, no SD).
Using Docker, I installed since a long time a lot of servers on it (Mailu, Wordpress, Nextcloud, Navidrome, Calibre-Web, Portainer, Kopia…). It works quite well and I absolutely don’t want to take any risk to lose that.
Now, I’d like to try DietPi and see if it would be lighter and support my containers better.
So I’d like to install DietPi in dual boot mode in an empty partition of my HDD without formating what I already have, w/o having to use an SD card, … and reuse my exisiting docker install (my docker repo is already isolated).
All I’ve found is PINN or BerryBoot and you have to start from scratch (or I haven’t figured out how to do it).
Eventually, if DietPi works fine, I’ll switch to DietPi and remove RaspberryPi OS.
Any idea welcome!
I doubt this is possible the way you like. You could try DietPi within a VM on your desktop computer. Yes, it might not simulate ARM based SBC but will give a feeling on the usage of DietPi. If your stuff is inside a container, it might not make a huge difference for using RPI OS or DietPi on your SBC.
Thanks @Joulinar but I 'd like to make sure it works “in place” with my existing containers, volumes, …
Furthermore, it means transferring hundreds of GB from my Pi to the VM
Simulating that on a VM will, as you say, give me a feeling of DietPi but it’ll be far from ensuring me it works in real conditions…
This wouldn’t make sense either, as ARM containers can’t be used on x86 systems. However, if you want to get a real live feel without risking your data, you will need to clone your existing data to play with it.
There is no other option than to boot from an SD card and mount the hard drive in DietPi. However, this involves some configuration effort as we use a different file system structure for Docker to store data. It will not be the same directories if you use our script to set up Docker. Hence the recommendation to play inside a VM to get a feeling for how we set up Docker and where the data is stored. At least if you use our tooling. You are of course free to install Docker yourself.
One other thing to consider is that NextCloud have stopped support for their docker image release path.
Over the recent holidays I took down my Docker Pi server and my DietPi one, and moved everything except NC to DietPi (which offers Docker and Portainer) and then rebuilt the former Docker Pi using the dedicated NC image.
So if you want NC to stay up to date and get fixes, then your Docker solution will need replacement anyway…
Well, the docker version of nextcloud is maintained by the community and is updated regularly. See Docker ==> the images are updated just a few days after the new NC releases. I am using this since a long time w/o any issue… (except that cron is not included)
Also, there is the AIO version which is maintained by NC: Docker
