47 minutes ago, stefan44 said:

I have a problem with docker inside LXC containers - all extractions are very slow and it takes about 30 minutes to run docker container for the first time when it installs all dependencies.

Can you please share a bit more details?

What container are you using, what disk are you using, what Backing Storage type are you using. What path are you using?

 

Please also post your Diagnostics.

 

Just as a side note, I updated all my Docker container images a few days ago and I build them inside a LXC container (about 15GB of Docker images) this took around ~1,5 hours, which seems totally fine to me because I have around 160 Docker containers to update, you also have to include the installation from all the necessary packages inside the container images and upload to DockerHub and GHCR.

Ok, I double checked and my problem was caused by using the wrong path in the LXC settings (/mnt/user/...). 
I changed that and everything works fine. Thanks for your help.

Edited June 10, 20242 yr by stefan44

On 5/24/2024 at 3:10 PM, ich777 said:

I don't know anything about Turnkey, can you explain that a bit in detail, is this a Distribution or something that gets installed or is Turnkey installed in a container?

Turnkey is a set of custom Linux Distributions that are set up for specific usecases. Each use case gets its own installer, such a a Wordpress server, or JS dev stack or MySQL server or a LAMP stack.

 

Turnkey has both baremetal and LXC instances, and Proxmox includes the LXC instances for use in their system. Proxmox uses their own custom branded LCX and do the work to make them work there.

 

https://www.turnkeylinux.org/

 

They are siimilar but orthogonal to the Bitnami style APP/USECASE focused setups.

17 minutes ago, BillDStrong said:

Turnkey has both baremetal and LXC instances, and Proxmox includes the LXC instances for use in their system. Proxmox uses their own custom branded LCX and do the work to make them work there.

Thanks for the explanation.

 

This is something that I plan to release, basically pre-made container archives witch certain applications installed that can be downloaded directly through the CA App.

 

I already have a few proof of concept containers, the most complete one is here.

 

BTW, this container can already be installed:

1. Open a Unraid terminal and execute:

   wget -O /tmp/lxc_container_template.xml https://github.com/ich777/unraid_lxc_pihole/raw/main/lxc_container_template.xml

2. Open a browser and go to http://<YOUERSERVERIP>/LXCAddTemplate
3. Install it

8 hours ago, ich777 said:

Thanks for the explanation.

 

This is something that I plan to release, basically pre-made container archives witch certain applications installed that can be downloaded directly through the CA App.

 

I already have a few proof of concept containers, the most complete one is here.

 

BTW, this container can already be installed:

1. Open a Unraid terminal and execute:

   wget -O /tmp/lxc_container_template.xml https://github.com/ich777/unraid_lxc_pihole/raw/main/lxc_container_template.xml

2. Open a browser and go to http://<YOUERSERVERIP>/LXCAddTemplate
3. Install it

I am going to try out your pihole container now. This is a very cool feature, if it means we will be able to do the same ourselves.

 

I will say Turn key has more than 100+ applications they have been finetuning for more than a decade, and have other niceties such as backup to S3 and other features built in. Adding them is an easy win for you not having to support all those apps.

 

Turnkey is based on Debian Stable, and they provide support for their installs.

 

The apps they provide are less for home use like pihole is, and more for business and work related things. Wordpress setups, CRM, Storefronts etc.

 

They are great to practice on as a dev environment before pushing them to a live server. I think they would be orthogonal to what you are doing.

 

Anyway, thanks for looking.

Is it possible to have the lxc path set to something else than the cache or the array?

I am trying to put it on a separate nvme that I use for all my docker containers and it doesn't accept the path.

 

/mnt/disks/Samsung_SSD_970_EVO_Plus_1TB_S4EWNF0M532569N/lxc

 

4 hours ago, SolidFyre said:

 

Is it possible to have the lxc path set to something else than the cache or the array?

 

Sure, look at the example, you are missing the trailing /

do you have a recommend path for updating containers to next gen containers of same distro?

Ubuntu as example

if I edit the source file and distro upgrade, it will upgrade off the old version and install the next gen packages.
 

5 hours ago, bmartino1 said:

do you have a recommend path for updating containers to next gen containers of same distro?

Do it as usual like if it's installed on a physical machine, nothing would stop you from doing a distribution upgrade.

 

5 hours ago, bmartino1 said:

Ubuntu as example

If you execute something like from within the container should do the job just fine (please note that this is specific to Ubuntu) :

apt update
apt install -y ubuntu-release-upgrader-core
apt full-upgrade -y
do-release-upgrade

(here the release upgrader is also installed because it is not installed IIRC)

 

5 hours ago, bmartino1 said:

if I edit the source file and distro upgrade, it will upgrade off the old version and install the next gen packages.

No, LXC is basically a VM but with shared resources/Kernel and you have to upgrade it manually. It does nothing on it's own because it acts like a VM.

Good evening. Today I made some changes to my server which required moving a couple of DebianVNC LXC containers I created quite awhile ago. I moved them and updated the configs and saw they started but I did not check if they got any further before completing an unrecoverable change to the disk they previously lived. No big deal, I thought, they are handling something simple and easy to setup, I'll just create new containers. Unfortunately, it looks like the DebianVNC option is no longer available. If the feature is no longer a simple button, does anyone happen to have a copy+paste of the commands to install the necessary packages before I try to figure it out on my own?

1 hour ago, mournful-hive3872 said:

If the feature is no longer a simple button, does anyone happen to have a copy+paste of the commands to install the necessary packages before I try to figure it out on my own?

Please give me a bit and I will present a solution that is easy to install.

@mournful-hive3872 please make sure to update the plugin before doing the following because I pushed a bugfix to the plugin:

1. Open up a Unraid terminal and execute this command:

   wget -O /tmp/lxc_container_template.xml https://raw.githubusercontent.com/ich777/unraid_lxc_debian_novnc/master/lxc_container_template.xml

2. In your Browser navigate to: http://YOURSERVERIP/LXCAddTemplate
3. Click "Apply"
4. Wait for the Done button to appear (this can take a bit depending on your Internet connection)

After that you have a fully Debian Bookworm container as before, you even can click the container icon and select WebUI which will take you to the WebUI from the container:

 

Hope that helps.

2 hours ago, ich777 said:

 

Hope that helps.

Thank you so much, I'm back up and running! You are an invaluable member of this community, sir, and I hope you know how much you are appreciated!

Hey All,

 

I'm running the Unify controller following the instructions here: 

 

 

During the update command I get the following error.  

 

 

root@UniFiController:/# sudo apt-get update && sudo apt-get install unifi -y
Get:1 http://security.ubuntu.com/ubuntu jammy-security InRelease [129 kB]
Hit:2 http://archive.ubuntu.com/ubuntu jammy InRelease                                                                          
Ign:4 https://repo.mongodb.org/apt/ubuntu bionic/mongodb-org/3.6 InRelease                                                      
Hit:5 https://repo.mongodb.org/apt/ubuntu bionic/mongodb-org/3.6 Release
Get:6 http://archive.ubuntu.com/ubuntu jammy-updates InRelease [128 kB]
Get:7 https://repo.mongodb.org/apt/ubuntu bionic/mongodb-org/3.6 Release.gpg [801 B]
Ign:7 https://repo.mongodb.org/apt/ubuntu bionic/mongodb-org/3.6 Release.gpg                  
Get:3 https://dl.ui.com/unifi/debian stable InRelease [2,292 B]              
Get:8 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages [1,791 kB]
Get:9 http://archive.ubuntu.com/ubuntu jammy-updates/universe amd64 Packages [1,100 kB]
Reading package lists... Done                         
W: https://repo.mongodb.org/apt/ubuntu/dists/bionic/mongodb-org/3.6/Release.gpg: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details.
W: GPG error: https://repo.mongodb.org/apt/ubuntu bionic/mongodb-org/3.6 Release: The following signatures were invalid: EXPKEYSIG 58712A2291FA4AD5 MongoDB 3.6 Release Signing Key <packaging@mongodb.com>
E: Repository 'https://dl.ui.com/unifi/debian stable InRelease' changed its 'Codename' value from 'unifi-8.1' to 'unifi-8.2'
N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.
root@UniFiController:/# 

 

never mind, I can't read.  There was a note at the bottom that walks you through updating.

 

thanks all.

7 hours ago, Flyinace2000 said:

Hey All,

 

I'm running the Unify controller following the instructions here: 

 

 

During the update command I get the following error.  

 

 

root@UniFiController:/# sudo apt-get update && sudo apt-get install unifi -y
Get:1 http://security.ubuntu.com/ubuntu jammy-security InRelease [129 kB]
Hit:2 http://archive.ubuntu.com/ubuntu jammy InRelease                                                                          
Ign:4 https://repo.mongodb.org/apt/ubuntu bionic/mongodb-org/3.6 InRelease                                                      
Hit:5 https://repo.mongodb.org/apt/ubuntu bionic/mongodb-org/3.6 Release
Get:6 http://archive.ubuntu.com/ubuntu jammy-updates InRelease [128 kB]
Get:7 https://repo.mongodb.org/apt/ubuntu bionic/mongodb-org/3.6 Release.gpg [801 B]
Ign:7 https://repo.mongodb.org/apt/ubuntu bionic/mongodb-org/3.6 Release.gpg                  
Get:3 https://dl.ui.com/unifi/debian stable InRelease [2,292 B]              
Get:8 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages [1,791 kB]
Get:9 http://archive.ubuntu.com/ubuntu jammy-updates/universe amd64 Packages [1,100 kB]
Reading package lists... Done                         
W: https://repo.mongodb.org/apt/ubuntu/dists/bionic/mongodb-org/3.6/Release.gpg: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details.
W: GPG error: https://repo.mongodb.org/apt/ubuntu bionic/mongodb-org/3.6 Release: The following signatures were invalid: EXPKEYSIG 58712A2291FA4AD5 MongoDB 3.6 Release Signing Key <packaging@mongodb.com>
E: Repository 'https://dl.ui.com/unifi/debian stable InRelease' changed its 'Codename' value from 'unifi-8.1' to 'unifi-8.2'
N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.
root@UniFiController:/# 

 

review:
 

You have to fix your source list. and grab the gpg key and sign/secure it.

https://help.ui.com/hc/en-us/articles/220066768-Updating-and-Installing-Self-Hosted-UniFi-Network-Servers-Linux

 

This was my end script to maintain and use mongo db 4.4:
https://repo.mongodb.org/apt/ubuntu

#older 3.6
#deb [trusted=yes] https://repo.mongodb.org/apt/ubuntu bionic/mongodb-org/3.6 multiverse

deb [trusted=yes arch=amd64 signed-by=/etc/apt/trusted.gpg] https://repo.mongodb.org/apt/ubuntu/ bionic/mongodb-org/4.4 multiverse 

#Depricated key?
deb [trusted=yes arch=amd64 signed-by=/etc/apt/trusted.gpg] https://repo.mongodb.org/apt/ubuntu/ jammy/mongodb-org/4.4 multiverse

Sometime to get unifi to update:
apt-get update --allow-releaseinfo-change

 

Edited July 7, 20241 yr by bmartino1

4 hours ago, bmartino1 said:

You have to fix your source list. and grab the gpg key and sign/secure it.

Hey! Thanks for creating the tutorial.

Are you interested in a premade container archive which users easily can deploy?

10 hours ago, ich777 said:

Hey! Thanks for creating the tutorial.

Are you interested in a premade container archive which users easily can deploy?

 

I would love too! But I don't know the first thing about how to create and deploying a LXC.

Earlier is why I asked about proxmox / this plugin on how i could add my own template.

I would love to learn and add something similar.

In theory, I would need to add a lxc container conf and a way to add secondary Container URL to the lxc templates:

Not sure if you can add 3rd party or not.
 

I'm not sure how the archive system would work. I have no problem making a default snapshot of a premade image.

Not sure how that would work and be implemented:

I'm not sure if the plugin has the LXC/LXD commands:

 

Turn your container into an image and export it.

lxc stop NAME

lxc publish NAME --alias backup

lxc image export backup .

lxc image delete backup

1 hour ago, bmartino1 said:

I'm not sure if the plugin has the LXC/LXD commands:

No because LXD is now in the hands of Canonical and I am not planning to include Incus.

 

1 hour ago, bmartino1 said:

Turn your container into an image and export it.

It's actually way easier, at least I think.

The LXC plugin for Unraid already supports templates, take for example this repository:

https://github.com/ich777/unraid_lxc_pihole

 

You just do the following directly on your server:

1. Open up a terminal and issue this command:

   wget -O /tmp/lxc_container_template.xml https://github.com/ich777/unraid_lxc_pihole/raw/main/lxc_container_template.xml

2. After that go to: http://<YOURSERVERIP>/LXCAddTemplate
3. Change whatever you need to change and click Apply
4. Wait for the Done button to appear

 

If you want to create such a template just clone the repository to your Unraid server, look into the build directory, do the necessary changes for your application (create scripts/files and startup routines), open up "createLXCarchive.sh" in the main directory, change the variables here (except for line 9 and 11) to fit your needs and finally execute the script.

 

What it does in the background is it executes each script in the build directory starting with a number in a temporary LXC container and produces a highly compressed LXC container for you to put in the releases tab here.

 

It maybe sounds a bit complicated but it is really not, you can for example search my GitHub for example containers (the linked above is the first documented one).

 

For more information please feel free to send me a DM.

Thank you ich777
While I have a github account and can share and release code.
https://github.com/bmartino1?tab=repositories

ATM this git and github is fairly new to me and alot of my code stuff is in alpha or test as i was testing and reviewing other's code.

I'm more looking to export the entire rootFS folder. With config. to transfer competed edits, gpup keys and other via GNU GENERAL PUBLIC LICENSE. Some things can get weird and copyright tricky fast...

But exposing the root FS to GitHub opens it up to potential bad actors as the secrets and others are exposed form the debain os...

Which is why I could see sharing a snapshot instead.(Maybe...)

Quick Review of your lxc template. Its an interesting way to share the lxc and use pi hole... Incidentally, I have recently set up a similar LXC using Pi hole with Cloudflare /stubby /unbound in a debian lxc container. Its setup and working properly as well. Seeing your template, I may be looking to add lan cache to it.

ATM I think it's easier to explain why I did xyz and share the commands I ran then it is to try to rebuild and generate a full template. ATM this is Not as easily exported or setup to use for a client/user to point click...

So I would have 2 lxc container template Ideas I would like share to the community when I/We/ETC are done and capable. I will dig into it more tomorrow when i have more time.

 

I will need to see if I can transfer a snapshot to restore to a friend's lxc as a test and then explore what in the snapshot. Not sure if a snapshot is as exposing of the root system. or what I should pull to keep a general backup of instulation. As i have used other apt key programs to install all apps and copy all configs I have had and used before in the past to move systems form PC to PC.... 

This way I could guide a client/User to make a XYZ lxc container named the same in their general lxc path and download/git clone the source. Then restore snap and be done. Some small lxc conf edit may be required.

IDK if it more work to make a lxc image. to IDK use proxmox to make a image and export it to github. Then again potential use the wget/ lxc template download command. Similar to adding a lxc template repository you posted earlier. I have options regardless. Just not sure what path is best to take and better for security/client use.

I'm not sure what " Incus." but I understand not wanting to implement and use Canonical lxc/lxd new codes and system.

I need to do some more research.

2 hours ago, bmartino1 said:

I'm more looking to export the entire rootFS folder. With config. to transfer competed edits, gpup keys and other via GNU GENERAL PUBLIC LICENSE. Some things can get weird and copyright tricky fast...

Oh wait, we are talking about completely different use cases here.

You basically want a system that allows you to transfer your images to other machines correct?

My use case would be just to make pre-made container archives available for users to download and deploy through the CA App.

 

3 hours ago, bmartino1 said:

Which is why I could see sharing a snapshot instead.(Maybe...)

This is already possible but I would rather recommend doing that through the included Backup function which I ship with the Unraid plugin.

This will basically compress the rootfs including the config (or not compress it, just how you set it up) and you easily can transfer it over to another or even the same system and deploy it as a new container, similar how Snapshots work but also different since this can be any location on your server.

 

The backup function is both available in the WebGUI (when you configure it in the LXC settings) or from the command line, open up a Unraid terminal and issue:

lxc-autobackup --help

or in the WebUI go to the LXC settings and click Backup:

 

3 hours ago, bmartino1 said:

But exposing the root FS to GitHub opens it up to potential bad actors as the secrets and others are exposed form the debain os...

This is not really an issue for my use case since as said above my use case would be only to deploy premade container images for easy deployment to end users, similar like Docker works.

In my PiHole container the SSH keys for example are deleted before the container archive is created and the keys will be created on first start from the container by this script, so to speak even the keys don't leak out to GitHub.

 

Again, this is a completely different use case from what you are looking for.

 

3 hours ago, bmartino1 said:

Quick Review of your lxc template. Its an interesting way to share the lxc and use pi hole... Incidentally, I have recently set up a similar LXC using Pi hole with Cloudflare /stubby /unbound in a debian lxc container. Its setup and working properly as well. Seeing your template, I may be looking to add lan cache to it.

I would recommend that you just deploy it and try it out how my solution works and LANCache is completely optional.

 

3 hours ago, bmartino1 said:

ATM I think it's easier to explain why I did xyz and share the commands I ran then it is to try to rebuild and generate a full template. ATM this is Not as easily exported or setup to use for a client/user to point click...

My take on that was for you to be able to create a Unifi container archive for others for easy deployment.

 

3 hours ago, bmartino1 said:

This way I could guide a client/User to make a XYZ lxc container named the same in their general lxc path and download/git clone the source. Then restore snap and be done. Some small lxc conf edit may be required.

But why would you do that?

I built the template function because it is way easier to deploy for users (just a wget and the WebGUI part) currently and it will be even be easier when the templates are supported by CA.

 

Basically what my approach (for containers that you want to share with the community) is similar to the Backup function it creates a highly compressed container archive from a temporary container that users can easily deploy with just the necessary packages and scripts to run the application(s) inside the container). However I don't recommend use the Backup function to share containers with other users because it is not designed for that.

 

3 hours ago, bmartino1 said:

IDK if it more work to make a lxc image. to IDK use proxmox to make a image and export it to github.

I really don't like the idea of the image because it would be way, way easier to leak out some of what you've mentioned before, is way less flexible and of course don't forget how much increase this means in terms for filesize.

 

3 hours ago, bmartino1 said:

I'm not sure what " Incus." but I understand not wanting to implement and use Canonical lxc/lxd new codes and system.

Incus is basically a fork from LXD because LXD was ripped out of the hands from the community from Cononical without a real warning, so to speak Incus is the new LXD, but again I won't include Incus or LXD in the Unraid plugin.

 

 

I would really recommend that you try some of the images for example this image:

https://github.com/ich777/unraid_lxc_debian_novnc

which containers a fully fledged XFCE desktop environment that you can access through noVNC.

You just have to always download the RAW template file to: /tmp/lxc_container_template.xml and then visit the site: http://<YOURSERVERIP>/LXCAddTemplate to install it.

 

The templates also fully support custom container icons and also a WebGUI button like it is the case for Docker, this is how everything looks on my server:

Quote

Oh wait, we are talking about completely different use cases here.

You basically want a system that allows you to transfer your images to other machines correct?

My use case would be just to make pre-made container archives available for users to download and deploy through the CA App.

 

Correct, I was looking to share my created image to another unraid system as a group of friends and myself run similar services, dockers, lxc apps... and are in a ring for backups between each other. I was looking to copy or move my working lxc container to their system...

Incidently In a way this could also be done with the share CA premade container option. I'm still digging into how the containerize and code - run xyz and to make image for Unifi per your github and examples. as it gets trickey with the changing the Repository and how unifi is still using a bionic repo for the package and with ubuntu/debian specially jammy reaching potential EOL. with the recent change on secure repository and the apt-key sytem being deprecated. So i need to find the coands to add the repository and make a script that runs to make the CA container

 

Or export the already done container. In either case, its easiest on me to just type up a how to guide with each step pictures and commands. But as apps, repositories and version of Ubuntu change over time, that mileage may vary.

My other concerns ar, by the time I get to the lxc template.
Mongol db 4.4 will be os is about to hit EOL in April so that will be the next hurdle to jump which may change how I would want to have a client go to CA and download a premade image. Since Pete Asking has a docker version and it works well, but dev is slow I went LXC route.

I'm currently in dev on this and have not posted stuff to GitHub for a test of your wget lxc template and template add. ATM with the beta 7 release this has more of my attention and testing. so while i plan to do this dev on it has slowed/stopped.

 

This was why I was looking at the lxd commands to backup and move the image.

12 minutes ago, bmartino1 said:

This was why I was looking at the lxd commands to backup and move the image.

Again, lxc-autobackup is what you are looking for on Unraid.

 

12 minutes ago, bmartino1 said:

Correct, I was looking to share my created image to another unraid system as a group of friends and myself run similar services, dockers, lxc apps...

Then you should use the Backup function.

 

12 minutes ago, bmartino1 said:

my working lxc container to their system...

There is already a plugin out there that I look for feedback and I have currently stopped development because of real life but I will continue when everything calms a bit down:

 

12 minutes ago, bmartino1 said:

as it gets trickey with the changing the Repository

Why, you can always pass over a variable or set it in a file or even grab the new location automatically, there are so many ways to do it.

 

12 minutes ago, bmartino1 said:

Or export the already done container. In either case, its easiest on me to just type up a how to guide with each step pictures and commands. But as apps, repositories and version of Ubuntu change over time, that mileage may vary.

Again, what you find on my GitHub and as I explained above this is just a automated way of creating a container with all packages installed and the best thing is that you don't have to write tutorials, you do that right in the script that creates and packages the container.

 

12 minutes ago, bmartino1 said:

My other concerns ar, by the time I get to the lxc template.
Mongol db 4.4 will be os is about to hit EOL in April so that will be the next hurdle to jump which may change how I would want to have a client go to CA and download a premade image. Since Pete Asking has a docker version and it works well, but dev is slow I went LXC route.

LXC containers are static and similar to a VM, if you want control over what is installed then I would always choose a LXC container over a Docker container because you never know what breaking changes are introduced when making an update or the container even auto updating. That's why I have my Homeassistant and PiHole container in a LXC container because PiHole is way easier to manage in a LXC container than Docker and you don't have to deal with any port trickery or similar.

 

A user that installs a LXC container must be well aware that he is responsible for updates...

 

12 minutes ago, bmartino1 said:

I'm currently in dev on this and have not posted stuff to GitHub for a test of your wget lxc template and template add. ATM with the beta 7 release this has more of my attention and testing. so while i plan to do this dev on it has slowed/stopped.

I think you will find time for that because, the container is set up in 1 minute.

 

 

However again, just try it out and then we can talk, it is always a bad idea to talk about stuff when you didn't tried it and if you don't want to use my approach I'm also fine with that.

Not sure if you noticed but it seems like ipv6 broke with Unraid 7. Absolutely no functionality apart from a local-link which is unusable.