Beiträge von lordofpc734

    Hi
    I run OMV on a PC of mine together with docker (docker-compose plugin)
    OMV itself is accessible via the br0 bridge interface (192.168.2.45)
    I have two containers, jellyfin and pihole, (192.168.2.20, 192.168.2.30) they use the macvlan interface (named netbr0). This works and there are no issues...until the host itself attempts to access these two containers.
    To resolve this, a bridge must be added allowing the host to connect to the macvlan containers
    (https://www.networkshinobi.com…iners-running-on-macvlan/)
    I ran the following command
    ip link add netbr0 link br0 type macvlan mode bridge

    ip addr add 192.168.2.43/32 dev netbr0
    I then proceeded to bring this interface up.
    if my understanding is correct, this adds a new bridge interface, "connecting" it to netbr0 (the name of the docker macvlan interface). The bridge has an ip of 192.168.2.43.
    then, per that webpage, I added routes to my containers:

    ip addr add 192.168.2.30/32 dev netbr0

    ip addr add 192.168.2.30/32 dev netbr0

    This works, I'm not sure if it's the best way to go about this, but it works, OMV can now ping these two containers and I can use tailscale on OMV and successfully connect to these containers.
    In summary:
    Problem: These changes I made are not permanent and will get removed on every reboot. If my understanding is correct, OMV uses netplan.
    I found these two config files under /etc/netplan

    10-openmediavault-default.yaml,  60-openmediavault-br0.yaml
    here is where I get confused, should I create a new yaml file or edit 60-openmediavault-br0.yaml?
    looking at netplan documentation's tutorials, I'm not sure which situation applies to my case (Introduction - Netplan documentation perhaps?)
    attached below you will find a full system report and the contents of the netplan config file. I would appreciate any help
    system report
    netplan 60-openmediavault-br0.yaml

    Just mount the system stick in any running system and change your fstab. It is that simple. Google how ro get uuid of disk in linux and change the /dev/sdc parts to uuid paths. Thats all.
    For non standard installations use the debian minimal iso and install omv via apt as it is suggested in the docu.
    I hate when people make mistakes, dont read docu, dont know what they do to just scream that this could have been avoided when a non paid developer would have spent another 50+hours in changing an installer. This work has been done by debian and you are free to use it.
    Actually my first post had the solution to your problem and by googling the few words you may not know like fstab or chroot, maybe uuid, you would have understood the point quickly. People are not thrilled to become your personal nonpaid administrator. Usually all are glad to help, but you should do your part and google what you get for answers. Nobody wants to write the same stuff 1000 times or add sources to everything in every post.

    sorry i was busy reading that other post. i think you misunderstood what i said. i never blamed anyone for this. i just wanted to know how to install omv on a partition. thats all. also i know all of those words you mentioned. uuid, chroot, etc. i was trying to do what you said when geaves posted that guide and then i decided to follow that guide. (because it was easier). now do you think i should go to fstab and change its values ?

    Hi. i have a netbook which im trying to install omv on. first i formatted the internal hard disk to 2 partitions. 1 for the OS (8gb) and the rest for data (923 gigs) i did this using gparted
    it installed fine and all and booted into omv. while setting it up, i noticed that it didnt respect my choices and just formatted the drive and installed omv on it. as a result of that, i cant use the drive for shared folders.
    so i nuked the thing and decided to install OMV on a 4 gig usb stick. it went fine but after installing it just shows those errors. at the end it says ALERT ! /dev/sdc1 does not exist. dropping to a shell and then it goes to a thing called busy box . i noticed that there is a thread already about this but that was for people who had raid. i do not have raid.