วีดีโอ

Hello, you need to add compose folder on compose settings.

You're welcome! I'm glad I was able to explain it, hehe. Cheers!

Hi, I haven't had this experience yet. I would check if all the mapped folders within plex are still correctly linked / mapped. Example: movies library -> movies folder etc.

You are welcome! Cheers!

Hi there, you can try cloning the drive. I'm am not sure what would be the best approach to migrating all the containers, etc.

Hello, since both use macvlan, they can each have their own ip address. As far as which dns server answers your request, it will be based on which ip you send the traffic to. Pihole or adguard.

Thanks, for the feedback. Much appreciated.

Thanks for the support. Much appreciated!

Thanks for the sub! Appreciate the support!

Hello, the reason for the error is because of the file permission on compose folder or the appdata folder. Go to Shared Folders, highlight compose folder and click on the top check mark it says "access control list" and make sure the owner is root, Group is users, permission should be read/write/execute for other read/execute. Repeat this steps on appdata folder as well. Let me know if this works for you. Sorry for the late reply

Thanks a lot!

Hello, you would need to recreate the container image using the same docker file. Then stop your pihole container and start it again. This will load the new container that you created. If you want to play it safe, you can copy the pihole files and rename the folder and create a new compose file. You would ssh into your omv and and find your pihole install folder in the video mine is called piholeunbound. cp -R piholeunbound piholeunbound2 this is just going to copy your current pihole folder to another folder. Then create a new docker file and copy the old one but make sure you add a tag let say 1 and then pull and create container. What this will do is create a new piholeunbound:1, so then on the new yaml / compose file you would use 1 as a tag. Example: piholeunbound:1 under image: Now you would create a new compose file and name it different than the old one. Make sure you change the container name in the yaml file and also the install path under volumes. Instead of piholeunbound/... it will be piholeunbound2.. this will be different if you copied the folder under a different name. Make sure you turn off the old one when starting new test one since the ip address will be the same. If for whatever reason the test one does not have your data DO NOT do this on your main piholeunbound container. Unless it all goes well then you can just rebuild the original docker file and stop the test one and start your original, this is assuming that tag is set as latest like in the video. Or you can also just continue using the test one. Hope this helps.

Hey, and is this a new install omv like the video? Or did you change the permission to the directory where the container are installing. This is a weird issue.

Thank you too! Cheers!

Hello, it sounds like the credentials were created wrong on the mariadb container. What you can do to test your mariadb container. You can console to it "docker exec -it mariadbcontainername bash" there you can try to connect to the nextcloud database using the following. mysql -u nextcloudDBuser -p Enter the nextcloudDBpassword and see if it connects. If not, the mariadb container credentials were set up wrong. You can delete mariadb container data (folder) and run the yaml again to recreate the mariadb database.

@@robwithtech thank you for the reply, unfortunately I am getting the same error after deleting mariadb appdata folder and recreating container (even tried .8 version) does the length of the password matter? I use 38 character length password for database user and root

I know there are some special characters that are not accepted in mariadb. I am not sure about the password length.

@@robwithtech I tried with simple password, but I think there is a permission issue:, in mariadb log file I see following: "2024-06-10 11:36:31 0 [ERROR] mariadbd: File '/config/log/mysql/mariadb-bin.index' not found (Errcode: 13 "Permission denied") 2024-06-10 11:36:31 0 [ERROR] Aborting"

I am not 100% certain what the user could be. Looking up that error shows premission issues where being installed. I would check in docker compose settings, what user and permission do you have? And then compared to what permission you gave the directory where you installed mariadb.

Thank you!

Hello, thanks for following along. As far as the data directory goes, you have to go into shared folders and select the data folder. On the top one of the icons, i believe it's called acl and see who is the owner and group. In my case i have root as owner and users in group. Read and write access for both. In this case, I can add the smb user to users group and they get access.

@@robwithtech oh thank u, now i isolate the nas and omv. thank u a lot of that. you will see another question about plex, its me again ;'( but i learn a lot, thanks to u ^^

Gracias amigo, saludos!

Hello, thanks for the feedback. As far as nano goes, it does not matter they are both text editors. What could be wrong is syntax or spacing. Make sure you don't tab inside the files. What you can try is adding 1 parameters at a time to identify which one is the issue.

I apologize. it's one of my first videos. I started zooming in on my other videos.

Thanks for the sub! Cheers!

Thank you, I appreciate it!

Glad to hear it! Cheers!

Hello, I did some testing. I see what you mean now. If you are only using 1 drive, your shared folder will just show as /data if the folder name is data. You can use that path as normal. When you add a secondary disk and create shared folders, it will show the long absolute path.

@@robwithtech Thank you for the fast reply Rob! OK so now setting up my VM for HAos I have two pools under KVM: isos and volumes and under KVM Volumes I also have 2 Volumes setup, under isos I have haos_ova-12.3.qcow2, and under volumes I have volumes.qcow2 with isos set at 32GB and volumes at 50GB. When I go to KVM ISOs tab I show no ISO listed even though I copied over the haos_ova-12.3.qcow2 file over to the isos folder that is shared on my network and I can see on my Windows 11 File explorer? So of course when I go to setup the VM in KVM I show nothing in the Optical Drive pulldown so I am stuck. 🥺

@@robwithtech Also would it help if I put a SD memory card in my Intel NUC? I have a SanDisk Ultra 256GB. The NUC has a Kingston 120GB (111.79GB) SSD installed in it.

Hey, the .qcow2 file wouldn't be picked up in the iso file since it is not an iso. That is an image file. So you would have to create a folder in the volumes and add it there. When you create your vm storage of the vm, you link it to the .qcow2 file.

You can, just keep in mind that sdcard has a limited amount of write cycles.

Hello, are you using the latest OMV iso? Also did you install omv-extras plugin? I have a newer video for this. But I never mess with anything to make the /srv path show up. The only thing you need to install is omv-extras plugin so your boot drive is shown in filesystems and you can create shared folders. Let me know if you get it working. th-cam.com/video/2hU8e61UE9w/w-d-xo.html

@@robwithtech yeah I have 7.1.1-1 (Sandworm) running with omv-extras listed under System and KVM listed under Services. Thanks for the link to you other video. I will watch it again to see if I am missing a step and report back.

Hello, I haven't seen this. Did you put the correct information on the creation of the macvlan?

@@robwithtech Hi Rob, yes, added the config and the macvlan was created automatically by the compose stack. I had been running this exact setup for years on a Rpi 4, but it started struggling a bit, especially since I was running Jellyfin as well. This exercise is to replace the Pi with a better machine.

You can create macvlan through the yaml file, but you need to specific the gateway subnet, etc. In this example, I create the macvlan via compose plugin, and then in Yaml, I use external so i can tell docker to use the macvlan just created. You can only have 1 macvlan per network interface.

@@robwithtech yes that's exactly what I've done.. not to worry, I'll figure out some other way to get it going. I was just wondering if anyone had seen this error before. Thanks for your assistance.

Hello, which one? Can you please specify the time in the video. Thanks.

@@robwithtech Thanks for answer. I want the Github link you used for portainer file copy and paste described on 22:34.

Here you go. You can go into homelab then docker compose you can see the containers there. github.com/robwithtech/

@@robwithtech Thanks Rob for your invaluable help. Now hands to work!!!

@@robwithtech Thanks for your help!

Hello, I think the image file would be .qcow2.

Hello, I will look into it. Thanks for the suggestion.

Hello, I will upload a video tomorrow covering upgrading nextcloud and mariadb containers. Stay tuned!

@@robwithtech thank you very much

You are welcome, video is posted in my channel! Cheers!

Glad you enjoyed it! Cheers!

Glad my video are helpful! Thanks.

Hello, I will work on that. Thank you for the suggestion and feedback. Cheers!

Hello, sorry for the late reply. Did you get it figured out?

Hello, I can. Is there anything that i should improve on? So i can keep in mind.

Hello, did you create the macvtap network according to your network?

Also, if you virtualize your openmediavault, then running kvm. You might want to look into enabling promiscous mode.

Hello, if you mean external, like accessing your nextcloud through the outside of your network. You would need to set up port forwarding.

@@robwithtech Thanks Rob. I'm accessing it through cloudflare for better security.

No problem. I'm glad you got it figured out.

Let us know what you decide. I have been running OMV for a while now. Haven't had any issues. Cheers!

Hi, it is not that bad once you do it multiple times.

Hello, did you create the macvlan as in the video?

Thank you!

Hello, the first time you start mariadb container, the username and password are set and will no longer take effect. If you want to reinput the username and password, you need to remove the container data. Also, the mariadb password won't work with certain special characters. Another thing to check is if you have portainer, you can make sure nextcloud container and mariadb container are on the same network "backend one"

Hello, you can stop the container and then highlight portainer and find the pull button on the top to pull the new image. After that, start it back up. You can download a backup file of portainer in case you run into any issues. (Menu select settings, scroll down to backup section) This only backups up portainer database and any stack files deployed from portainer. Hope this helps.

@@robwithtech Worked just fine thanks!

No problem, cheers!

Hello, it is actually quite simple. You can stop the container then highlight plex and pull the new container image (there is a button on top that does the "pull"). And then you start it after you pull the new image. Done. This will work if you used the latest tag on the image. If you didn't just specify new version. Hope this helps!

​@@robwithtech Hi, thanks so much for response. I was able to do it -- MUCH easier than I was expecting, as you said. In fact, I think I didn't even "stop" the container before clicking "pull" and it still worked. Seems like it knew to stop and restart on its own, pretty impressive. Cheers! 😊

No problem, cheers!

Glad you like them! Cheers!