Thank you! I was putting off installing Flaresolverr until I stumbled upon your video. You were straight forward but informative at the same time. It really helped that you explained yourself along the way. Cheers.
I've found that LXC's often vault far above their avg RAM usage, likely from system calls that result in user-space process launches, but it has been a big headache with netprobe monitoring, requiring me to basically FAR over-allocate RAM to my individual LXCs in order to prevent being spammed by netprobe by false-positives. So now, only when an LXC is *GROSSLY* overusing RAM am I alerted. It would be cool to campaign with the LXC team an improvement to have the most common Proxmox/Ubuntu kernel system calls that eventually hit user-space to be allocated from an overall shared RAM space for all LXC containers rather than on a per-container basis, so that we can more effectively monitor LXCs for unexpected RAM use. But YES, completely agree that unless a distro has a custom kernel or cannot run in Unprivileged mode, it's completely wasteful to use VM. LXC: It is the way...
If you shipped Flaresolverr with Docker then it should start everytime you boot the container. This keeps you from having to create a service to tell it to start when you start the continer as docker would automatically do that even if you havent logged in. The most beautiful thing about Proxmox and its LXCs is that Docker can be orchestrated within it the same way it would within or ourside a VM and both are super light.
the problem doing that , is that you put another container (docker) inside another container (lxc) and it's not "needed", creating a service and make it to start at the boot is actually not hard to implemente, if people dont want to do all of those thing, so yes they should use a docker who is more easy to use
i would suggest you to just docker compose it, that way you dont have to do all of this. Also you can use tags in prowler to define which indexers should use the flaresolver route cause not all indexers need it. Thanks for the video and other proxmox content
That's great for people who want a docker container environment. However, I want to use proxmox so I can spin up VMs or containers as necessary. I also don't want to run a VM just for docker since I have access to a lightweight container system (LXC) built right into proxmox. Also, if I FUBAR a setup in an LXC, then I just blow it up and try again and not have to worry about losing other containers.
I wish to use more LXC container but for me, the biggest “issue” is the fact is not so easy attach disks (HDD/SSD) to unprivileged container. I have a VM with a disk attached and samba installed. I wish to share a shared folder from this samba to the container. I don’t want attach the disk to the Proxmox host and mp the folder. At least with VM share folders is way more flexible.
To be quite honest, the first time you mount it, it is a pain but once you have done it a couple of time it's way easier and containers are well worth the effort when you think about things like uptime and backup time, a Pi-hole container DNS (in my homelab) can backup and restart over the network in under 4 seconds, try doing that with a virtual machine :). A VM virtualize every part of you machine down to it's core component while with a container you need to passthrought existing technology from the host to the container, which is why it's harder to deal with containers.
Don't know if you will read this or not, but how would you run something like authentik that doesn't have Linux instructions in their docs? I've cloned the repo, set up the config file and postgres db but I can't install the requirement.txt because it's not available in the repo.
Well, I apparently am having some issues with this one. Was fine as long as I am not connected to virt01. If I am connected to port vert0 I can pull everything. Not sure if that's due to my vpn potentially not working right on the openwrt side, etc. Going to have to pick someone's brain. Grrrrr....
This looked very scary (28GB/8MB): WARNING: Sum of all thin volume sizes (28.00 GiB) exceeds the size of thin pool pve/data and the amount of free space in volume group (8.00 MiB)
Thank you! I was putting off installing Flaresolverr until I stumbled upon your video. You were straight forward but informative at the same time. It really helped that you explained yourself along the way. Cheers.
Finally, the Holy Grail of LXC containerization!
I've found that LXC's often vault far above their avg RAM usage, likely from system calls that result in user-space process launches, but it has been a big headache with netprobe monitoring, requiring me to basically FAR over-allocate RAM to my individual LXCs in order to prevent being spammed by netprobe by false-positives. So now, only when an LXC is *GROSSLY* overusing RAM am I alerted. It would be cool to campaign with the LXC team an improvement to have the most common Proxmox/Ubuntu kernel system calls that eventually hit user-space to be allocated from an overall shared RAM space for all LXC containers rather than on a per-container basis, so that we can more effectively monitor LXCs for unexpected RAM use.
But YES, completely agree that unless a distro has a custom kernel or cannot run in Unprivileged mode, it's completely wasteful to use VM. LXC: It is the way...
Thank you!
awesome vid, I made this manually however there is an LXC container on helper-scripts now.
If you shipped Flaresolverr with Docker then it should start everytime you boot the container. This keeps you from having to create a service to tell it to start when you start the continer as docker would automatically do that even if you havent logged in. The most beautiful thing about Proxmox and its LXCs is that Docker can be orchestrated within it the same way it would within or ourside a VM and both are super light.
the problem doing that , is that you put another container (docker) inside another container (lxc) and it's not "needed", creating a service and make it to start at the boot is actually not hard to implemente, if people dont want to do all of those thing, so yes they should use a docker who is more easy to use
Docker adds another resource layer. I don’t see why, if you know Linux fundamentals, you would want that overhead.
i would suggest you to just docker compose it, that way you dont have to do all of this. Also you can use tags in prowler to define which indexers should use the flaresolver route cause not all indexers need it.
Thanks for the video and other proxmox content
That's great for people who want a docker container environment. However, I want to use proxmox so I can spin up VMs or containers as necessary. I also don't want to run a VM just for docker since I have access to a lightweight container system (LXC) built right into proxmox. Also, if I FUBAR a setup in an LXC, then I just blow it up and try again and not have to worry about losing other containers.
You’re confusing Linux containers with docker containers. Two different concepts.
This was a really good video. I can’t get prowlerr to use the indexer proxy. It always shows disabled. I saw I need tags but I am unable to add tags.
I wish to use more LXC container but for me, the biggest “issue” is the fact is not so easy attach disks (HDD/SSD) to unprivileged container. I have a VM with a disk attached and samba installed. I wish to share a shared folder from this samba to the container. I don’t want attach the disk to the Proxmox host and mp the folder. At least with VM share folders is way more flexible.
Also you can use the VM during a backup vs the LXC has to fully shutdown till the back up is done
To be quite honest, the first time you mount it, it is a pain but once you have done it a couple of time it's way easier and containers are well worth the effort when you think about things like uptime and backup time, a Pi-hole container DNS (in my homelab) can backup and restart over the network in under 4 seconds, try doing that with a virtual machine :).
A VM virtualize every part of you machine down to it's core component while with a container you need to passthrought existing technology from the host to the container, which is why it's harder to deal with containers.
@@Amwfilms If you don't have high availability and load balancing, you are doing it wrong
Sounds more like a lack of understanding than an actual issue.
enable --now (enable and starts at the same time)
Wow! Never knew it.
Thank you.
Amazing video!! liked, subscribed and shared.
Great video again, very helpfull !!
You set that container as dhcp, will it use a different ip if your server shut down/power outage etc?
Beginner here , how do you ensure the lxcs in the llan renew their dhcp leases?
Now just teach us how to export this lxc to use it later like we do with docker images please
Don't know if you will read this or not, but how would you run something like authentik that doesn't have Linux instructions in their docs? I've cloned the repo, set up the config file and postgres db but I can't install the requirement.txt because it's not available in the repo.
Well, I apparently am having some issues with this one. Was fine as long as I am not connected to virt01. If I am connected to port vert0 I can pull everything. Not sure if that's due to my vpn potentially not working right on the openwrt side, etc. Going to have to pick someone's brain. Grrrrr....
I see there is now a FlareSoverr Helper Script, anyone tried that yet?
Im a noob for the apt update. I typed all of you tyoed and it doesn't work
I couldn't spin it off on Debian 12, venv, systemd issues.
switch to Deb 11, I couldnt run pip on the requirement.txt, remade the LXC with Deb 11 and everything worked
@@RiseofBrutality666 thanks, I think eventually I did exactly that and it worked.
Ufffff LXC, bye bye docker
Which Linux distribution are you currently using?
He says Debian/Ubuntu at the end of the video, and it looks like it's the latest release Ubuntu is downloaded under his node.
Jones Mark White Paul Garcia Sarah
This looked very scary (28GB/8MB):
WARNING: Sum of all thin volume sizes (28.00 GiB) exceeds the size of thin pool pve/data and the amount of free space in volume group (8.00 MiB)