วีดีโอ

That is a reasonable point. However, I have a couple videos with chapters and my experience with them has been that subscribers come to me with questions because they skip over critical material. I try to keep my "editorial" content to a minimum and just present the material in an easy to follow, abridged fashion. "Incus Containers Step by Step" is one of those videos where not missing anything is critical to success. I will consider chapters in the future where viable. Thanks for the comments!

@@scottibyte that's fair enough :)

@@bwbuhse Be sure to join the chat chat.scottibyte.com/. Lots of folks there and I get a lot of input from other subscribers there to target future content.

I like Cryptpad and PSITransfer. I know I have an old video on PSITransfer. I also like YouTransfer and I have a video on it for sure. It's an old app, but my notes have the pertinent info to get you going.

Yes, who would have thought that NPM was the long pole in the tent? As it turns out, NPM is a web server like any other and so the same limits apply. Glad it helped. Drop by chat.scottibyte.com/ to say hi sometime.

@@raiden72 yes, agreed. However, the point of the presentation was really someone migrating from an ISP router to something like a Unifi router.

Glad to be of help. Stop by and say hi in the chat at chat.scottibyte.com/. My subscriber numbers are a clear indication that my channel has been highly effective at hiding. I've had the channel for four years and almost 275 videos.

Thanks Jon. Be sure to join the chat and say hi. chat.scottibyte.com

That would make sense in the commercial world use of redundancy but the audience here is not commercial use-case but the home-lab. Curious how a home-lab would have multipel clusters and WAN connections to bounce around for VRRP to live on their router (in this case UDM-P) ...

All my systems are distributed across 8 VLANs.

@@CalvinHenderson Oh, any "homelab" depending on how many "homes" and "labs" you can run.. ;-) It's more common in the 'pro' world, but to achieve real redundancy, servers and services should be span across differents sites, using multiples wan on each site :-) (i'm not a real home-laber, that is probably twisting my vision of things..)

People at ‘home’ are not running multiple sites across multiple homes. That is a commercial setup. I see you are one of the few that have multiple homes or connections via personal or professional and can use them all. Many people say they want multi-site setup’s but few can afford multi-sites just for a ‘home’.

​@@CalvinHenderson It's true :-) My job offers me a lot of opportunities (6months in europe/6months in south america + multi pro-sites).. it might not be the case for many peoples, tho, this video is still interesting and a very nice "learning support" for some of my co-workers :-) In the setup described, 8 VLANS, one site, multi homelab-servers.. it's a concept i'd call "RAIS" : Redundant Array of Inexpensive Servers :-D

Docker, like LXD and Incus are containerization technologies designed to isolate applications or components of applications to improve reliability. This is achieved either by providing a dedicated environment for the application to run or by isolating it from the host OS for interoperability concerns. Docker has the additional benefit of allowing application developers to deliver an "appliance" that runs the same way on every target system regardless of any dependencies that might be missing. Both NginX Proxy Manager and SearXNG are delivered as docker containers for this precise reason and the docker packaging makes those apps easier to deploy and more resilient against changes in the host environment.

@@scottibyte Yes, I know all that, but I still despise how docker works and avoid it like a plague. For one thing, relying on docker-compose deprives us of learning how to install apps natively, which is what I am primarily interested in.

@MarkConstable not all apps will have a native install for your OS of course. Docker excels because it provides a dedicated environment where an appliance can run reliably despite any dependency limitations imposed by your host OS. Docker exists in part because some apps are too fragile or complex to coexist with other apps.

@@scottibyte Then that is a red alert that I would not want to use those apps anyway.

@@MarkConstable To get around the need for no appliance configurations you are eliminating probably 70% of open source applications. I get wanting perform native installs. However, by that logic docker, flatpaks, snaps and appimages are all off the table for you.

Thanks Jim. The significant challenge is developing a procedure with absolute repeatability on every system it is deployed on with as simple as possible set of steps. This one is a more complex subject and not usually covered in regards to home labs and I felt the message needed to get out. Thanks for the kudos again!

Welcome. Be sure to drop by the chat and say hi. chat.scottibyte.com/

Unlike the IPv4 WAN address that your ISP assigns you via DHCP which changes, the IPv6 prefix allocation that your ISP assigns is fixed and so using IPv6 global addresses on devices on your LAN should not change.

Incus doesn't have a Native UI. It somewhat borrows (or can run) the LXD server UI. It's a bit limited because it has to be installed on each server it managers. LXConsole can manage both LXD and Incus servers and one instance of LXConsole can manage many servers. My LXConsole manages 8 incus servers and 2 LXD servers. Come on by chat.scottibyte.com/ if you have time and I can give you an overall briefing. Incus supports incus containers, incus VM's and Incus OCI containers (docker) at this point. You can view an incus server as being your own private VPS and LXConsole is a GUI that lets you spin up all three types of containers.

I agree that Ubiquiti is testing the waters. Regarding iSCSI, I have had maybe four videos exploring its application in the home lab. iSCSI really is an elegant solution even over 2.5Gbps. I would also like to see integration into an elegant web based portal using Unifi accounts with 2fa. I don't think I saw any mention of the CIFS shares being able to operate within a domain.

Precisely why I didn't present it that way.

@@scottibyte But probably since Incus now support OCI, it will be common method to run lxconsole. Yes, I know OCI support still need to be improved. BTW: Thank you for your videos.

​@@piotrtalarczyk8987I have at least one video showing how to use Incus volumes with OCI containers and you can use that method if you like for hosting LXConsole.

In general, I would suggest macvlan. Join the chat at chat.scottibyte.com/ to ask more.

and that's basically what the channel is all about. Infrastructure design/configuration in a nutshell.

As shown in the video, you would use NordVPN's tool to acquire the info from the wireguard connection. That allows you to perform the "wg" commands to get what you need. Did you reference the show notes at discussion.scottibyte.com/t/ubiquiti-unifi-wireguard-connection-to-nordvpn/452

@@scottibyte Thanks a lot for the feedback. What is the NordVPN's tool? How do I get the necessary information out of it? I can only choose the country I want to connect. I tried to follow your show notes but it is still not possible. I could manage to get wireguard-tools from homebrew but the command sudo wg does not show anything despite I'm connected via NordVPN client to a server.

@@doembele I am not really a Mac guy, so not sure I can advise. Do you not have a Linux machine around? Mac is a variant of BSD Unix and not Linux.

@@scottibyte Thanks for your help.

Yes, I am aware. However, the Unifi DNS doesn't support CNAME records and Unifi doesn't have granular ad blocking like Pi-hole. We have waited five years for Unifi DNS and perhaps another five it will be there.

Thanks. So, I recreated my instance following my guide and I was able to get the logo worked as described. Perhaps join the chat at chat.scottibyte.com/ to ask questions.

When you say "default storage" I am assuming that you mean using zfs as your default for the root file system as opposed to ext-4. Generally if you are using a zfs file system, there is a chron job that sets autotrim to run on a weekly basis. If you are interested in seeing the trim operation status on your default storage pool in incus, use "zpool iostat -r default". Just FYI, the chat is better for these discussions than TH-cam comments.

I use both Plex and Jellyfin. Jellyfin is super easy to host. Plex is the more complex use case and no one had yet covered the topic of hosting Plex in an incus OCI container. I like both apps and I consider the use case just a bit different. In my case, most of my media is hosted on Plex. I tend to use Jellyfin for my HDHomeRun live TV because it is just simpler than the network tuner configuration in Plex. That being said, I use it in Plex as well for live TV. Yes, I prefer open source when possible, however Plex is pretty close to an open source model in the way they manage, update, and support the product.

@@scottibyte thanks for explaining

Virtual disks require the loop driver to be mounted and the loop driver cannot be handed the boot process from grub. My advice is to use something like redorescue to clone the drive to other media. Perhaps the redorescue image could be made on an iSCSI target.

Thanks. Be sure to join the chat at chat.scottibyte.com/.

This is something that I can help with if you join the chat at chat.scottibyte.com/ as featured in every tutorial.

Sometimes they are great and sometimes, not so much.

@@jblow530 I don't understand. Incus storage pools via iscsi are not nested in any way. Containers operate inside of storage pools and whether they are hardware on the Incus server or iscsi is immaterial and involves no nesting of any kind.

@@scottibyte Well nested as in running a zfs file system at the virtualization layer (in this case incus) running on top of the phsycial (NAS) storage layer also running zfs - on the back end. When I tested zfs pools on hosts running ZFS as the native file system I ran into write bottlenecks (IOPS were about half) due to the multiple copy-on-write transactions. Was my experience at least with TrueNAS as the NAS back-end when I tested iSCSI targets, may not be the case with others.

@@jblow530 ohhhh, I never considered that. I think if one were running zfs as the host file system, then a "dir" storage pool actually makes sense because containers would be in zfs natively. In that case, creating a zfs storage pool only makes sense on a dedicated device as shown in my video. Having a zfs virtual pool on a zfs file system is not only redundant, but probably a bottleneck as you described. My hosts typically are ext-4 and so a zfs pool for incus makes sense.

@@animaniaTV thanks for the kudos!

@@GTRComputers-u9y 11? 12...

I have addressed accessing NFS storage from Incus/LXD before. Basically you map the target folder from inside of the container to the incus host. Then you use the mapped folder on the incus host as a mount point to either an NFS export or an iSCSI target. In the case of iSCSI, you could instead create an Incus storage pool that uses an iSCSI target.