Posts by 22/7

    I've decided to dust off my odroid hc2 that got shelved when I built my mitx nas.

    My odroid hc2 is now running armbian buster with 5.4.83 kernel and omv 5.5.22-1 (I believe).

    The hc2 has now been designated as the sole nfs/tftp server and pihole (omv docker).

    This frees up my mitx hardware to concentrate on proxmox or whatever else project I might throw at it. Fortunately I was able to use rsync and pull my nfs directory from my working mitx build to my hc2 build and my raspberry pis didn't notice the difference.


    Both is possible

    • run OMV (Debian) as a basis and install VM using cockpit (for example)
    • run Proxmox and run OMV in a VM on Proxmox; OMV is very lightweight, so you can still enjoy the ease of configuration

    OMV in a proxmox vm sounds ideal. Is there a way to "create a proxmox vm" from my "live omv installation"?

    I'm at a dilemma.

    I'm only using my omv installation for some very basic things.

    SMB shares, NFS and TFTP for netbooted raspberry pis, docker for one container currently (pihole), and I'm not using any fancy RAID or disk feature (zfs) or even unionfs.

    So, I think I'm one of the few people out there that omv is really just too much.

    I do want to use proxmox for testing different OS installs and setups and I can't do that easily with omv and cockpit (without headaches).

    So I'm thinking of scrapping omv altogether, loading up proxmox, and just setting up a debian vm that only does smb, nfs, tftp and pihole all in one. That way I can use more hardware resources for playing with other vms.

    Am I on the right path here?

    So I have OMV running on a micro atx board with an i3-8100 and 32gb RAM. The board can accommodate up to i9-9100.

    I also have pihole running in a docker inside portainer inside omv.

    I was wondering if I would be able to migrate to proxmox with my current processor/ram and run omv in its own vm and pihole in another vm?

    The reason I want to do this is because I want to play with other things (and os's) and I think having the ability to create vms (I am used to using esxi in an enterprise environment) would be better then me trying to get other os's to run through cockpit (and I have tried with no success).

    I don't need to virtualize alot...maybe 3 or 4 vm's max at any one time. So would it be easy to move my current omv to proxmox on my current processor/ram setup or should I look at another processor? Even with another processor how could I move omv to a vm in proxmox?

    I don't know enough about the rest, but were your upstream DNS settings passed as environmental variables during the original container creation or did you fill them in after you started it? If the former, you may have a problem, if the latter I recommend you change it.

    When I first set it up I changed the dns settings after the container had started.

    I just did an exercise on backing up the pihole configs so now that I have a documented backup and restore process it shouldn't be a bother now.


    Just checked the logs. Nothing seems to be amiss. No errors.

    Although, all I did this time was stop the container, verify the volume rw status, and then start the container. When pihole "lost" its settings was when I stopped the container, shutdown omv and then restarted omv. When omv restarted the pihole container was also restarted so I'm wondering if there is some sort of "default" container startup.

    For now I will monitor it though.


    Thanks. When I created the stack via a compose file my volumes did not have the :rw value in it. Time to update it.

    EDIT: Just checked and it was already set to writable.

    Is it normal for a pihole docker container to lose some settings after it has been stopped and then started?

    I recently added some fans to my case and I had to stop the pihole container before shutting down omv.

    When I brought omv back online my pihole container was already started but I had to redo my upstream dns settings, my conditional forwarding and my regex lists.

    Is there something I need to do to make sure my container settings are saved?


    Before I installed docker I changed the docker storage path to a folder in one of my mounted drives.

    The folder did not need to be a shared folder.

    The docker install created the folder I specified in the location and the permissions were set.

    I would say set your path first then save the setting then install docker.

    And don't set it to a shared folder. Just set it to a folder in one of your mounted drives and the docker install should create it for you.

    It looks to me like you at least have your hdd6 mounted.


    sudo blkid

    and look at the uuid for your mounted hdd6.

    Then remove the database entry that does not match your mounted hdd6 uuid.

    I haven't tried Yacht yet, but one of first things I'd be looking at would be easy MacVlan configuration.

    Being able to assign a separate IP address to a container is a desirable feature but it seems that configuring a MacVlan interface is an exacting exercise, with pitfalls, where the config doesn't work.

    I found macvlan configuration to be somewhat confusing at first. Especially when portainer was complaining about the gateway already being used.

    I now have a macvlan that is used by my containers and corresponds to my LAN.

    That was one of my suggestions

    1. Will it or can it handle docker-compose files? They are very popular with the OMV crowd and people don't always get the compose/stacks stuff. I might not have watched the video long enough if I missed it (sorry, working)
    2. Is there an easy way to update a container? If the restart option had another option to restart and pull new, people here would love that.
    3. Can the ports be auto-populated from the image with button click or something fast?
    4. Can the volumes be auto-populated from the image with a button click or something fast?
    5. Lots of people are using macvlan and it is confusing for many. Not sure how to make that faster but just a note.
    6. Might have missed this too but can people edit the settings of a running container and have it restart after changing the settings? Haven't needed that myself but the plugin could do it and people miss it in portainer.

    Most are already being worked. macvlan is on the radar now.

    1. Compose files are awesome. I found that deploying pihole, adguard and an apache test container were easier/faster with the compose files versus creating the container itself manually.

    2 & 6. In portainer, I found the duplicate/edit button for the containers. I stop the container, make the changes, then click deploy container again. It gives a notice that another container with the same name exists and that portainer will replace it. I select ok. Portainer does warn that the new container may not start if the new settings are incompatible. So far I have edited containers many times with this method.

    3. The ports section of portainer is a bit confusing. So a new intuitive method/process/interface would be a nice welcome.

    4. I haven't tested creating volumes after the container is created. But definitely more dynamic container creation and maintenance would be a great feature from my short experience.

    5. Macvlan for me proved easy to pickup though admittedly with some understanding of how portainer labels the fields and what is expected. I wish the IPAM DHCP driver was available already vs being something the user has to add themselves.

    The fastest easiest way I found for the pi4 is install pios buster.

    Then do the standard raspi-config setup and enable ssh.

    I highly suggest setting a static IP to the pi from your dhcp server and not in the pi.

    Once your pi is configured run the install script command for omv5. It will detect your pi4 and install. It will disconnect like you saw when it adds the network adaptor to omv. Simply reconnect your ssh session and verify the ip with ifconfig.

    Then browse to the omv gui.

    It really is a simple process on the pi4.

    My pi4 that I use to test was the guinea pig when I was trying to figure how to upgrade from omv4 to omv5.

    In that setup I installed pios to a 64gb usb stick and booted directly from it. Of course before that I updated the eeprom on the stable channel and enabled usb boot. I then directly installed omv5 using the script command.

    I believe you should be able to install pios directly to your 120gb ssd after you update your eeprom to enable usb boot. Once it boots do the raspi-config process to setup your pios and then install omv using the script command. There should be no reason why you need to "clone" at this point.


    Point taken. I have looked at newegg as well as manufacturers websites directly. I saw mini itx boards with onboard wifi (two antennas) sticking out of the io panel. I have seen boards with not enough sata ports, no m2 slots, m2 slots tight, m2 slots in a weird location (my asus prime board) and just all around anything in between.

    I order from many different places but admittedly try to get as much from one source as possible due to the recent world situation that has just cobbled delivery services.

    But I digress. I am not a hardware expert. I don't keep up with the trends.

    I'm still learning docker but I find portainer easy to get around.

    Granted there are still some things I am learning/finding along the way.

    Managing macvlans is way easier in portainer than using the docker commands. I'm not averse to ssh/command line but sometimes gui really is more efficient. I was able to create, test, delete and recreate macvlans all from portainer.

    The only thing I would like to see in portainer is all the possible labels in their respective areas instead of adding one and then figuring out what label belongs where.

    You're saying migrate so does that mean you are just moving files from one disk to another?

    Just copying files won't work as you have just found out. Every disk would have a different uuid. What you should do is use something like clonezilla and clone the entire source drive to the destination drive. Cloning keeps the uuid intact.

    I don't see why you can't just install pios directly to the ssd and then omv on top of that and be done. I have installed pios on a 64gb usb stick directly and it boots fine.