39 minutes ago, Mainfrezzer said:

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.

Everything is working over here.

 

TBH it is a little hard for me to test IPv6 since I only habe it internally but I can reach my containers through IPv6

 

What network type are you using? Bridge and IPVLAN or no bridge and MACVLAN?

 

In terms of network nothing changed.

10 minutes ago, ich777 said:

 

 

What network type are you using? Bridge and IPVLAN or no bridge and MACVLAN?

 

I noticed while running on a macvlan bridge. Then i swapped back to ipvlan bridge, dummy-saved the change in lxc and still nothing. Only a downgrade to 6.12.10 brought the ipv6 functionality back. ( i didnt bother checking beta1)

3 minutes ago, Mainfrezzer said:

I noticed while running on a macvlan bridge. Then i swapped back to ipvlan bridge, dummy-saved the change in lxc and still nothing. Only a downgrade to 6.12.10 brought the ipv6 functionality back. ( i didnt bother checking beta1)

Sorry but I really can‘t test what‘s different since I don‘t have IPv6.

 

Can you be a bit more specific what‘s not working?

Does the container not get a IPv6 or can you not reach it?

 

Nothing changed in Unraid 7 in terms for IPv6 AFAIK.

On 7/14/2024 at 9:47 AM, ich777 said:

 

 

Can you be a bit more specific what‘s not working?

Does the container not get a IPv6 or can you not reach it?

 

The container just start with ipv4 and the fe80:: address. They do not get a GUA or ULA Address. 


Edit: i upgraded straight back to 7 and this is how it looks:





Edit: Found a fix for the issue. Change your LXC config from

 

lxc.net.0.type = veth
lxc.net.0.flags = up
lxc.net.0.link = br0
lxc.net.0.name = eth0

to

 

lxc.net.0.type = macvlan
lxc.net.0.flags = up
lxc.net.0.link = br0
lxc.net.0.name = eth0

and its working again under unraid 7.

Edit-Edit: drawback of course is that the veth enabled communication between the host and container, that doesnt work with macvlan and requires the host access enabled


Edit-Edit-Edit. 

 

Quote

ip6tables -P FORWARD ACCEPT

Will resolve the issue with veth. The default policy for FORWARD changed from ACCEPT to DROP
 

Edited July 15, 20241 yr by Mainfrezzer
found a "fix" for unraid 7

is it possible to create / install lxc containers with the proxmox VE helper scripts ? on promox they run flawless but here on a "naked new lxc container" it seems they are not working:

 

https://tteck.github.io/Proxmox/#unifi-network-server-lxc

 

bash -c "$(wget -qLO - https://github.com/tteck/Proxmox/raw/main/ct/unifi.sh)"
   __  __      _ _____
  / / / /__   (_) __(_)
 / / / / __ \/ / /_/ /
/ /_/ / / / / / __/ /
\____/_/ /_/_/_/ /_/

Loading...
/dev/fd/63: line 516: whiptail: command not found
⚠  User exited script
 

 

 

Edited July 30, 20241 yr by Grobalt

1 hour ago, Grobalt said:

is it possible to create / install lxc containers with the proxmox VE helper scripts ? on promox they run flawless but here on a "naked new lxc container" it seems they are not working:

 

https://tteck.github.io/Proxmox/#unifi-network-server-lxc

 

bash -c "$(wget -qLO - https://github.com/tteck/Proxmox/raw/main/ct/unifi.sh)"
   __  __      _ _____
  / / / /__   (_) __(_)
 / / / / __ \/ / /_/ /
/ /_/ / / / / / __/ /
\____/_/ /_/_/_/ /_/

Loading...
/dev/fd/63: line 516: whiptail: command not found
⚠  User exited script
 

 

 

Install instruction for unif lxc here:

I'm working on a unraid template for this atm. Proxmox maybe...

https://github.com/bmartino1/Unraid-LXC-Unifi

5 hours ago, Grobalt said:

is it possible to create / install lxc containers with the proxmox VE helper scripts ? on promox they run flawless but here on a "naked new lxc container" it seems they are not working:

 

https://tteck.github.io/Proxmox/#unifi-network-server-lxc

 

bash -c "$(wget -qLO - https://github.com/tteck/Proxmox/raw/main/ct/unifi.sh)"
   __  __      _ _____
  / / / /__   (_) __(_)
 / / / / __ \/ / /_/ /
/ /_/ / / / / / __/ /
\____/_/ /_/_/_/ /_/

Loading...
/dev/fd/63: line 516: whiptail: command not found
⚠  User exited script
 

 

 

I have setup a crude way to acomplish the template...

Create debain lxc, restore form a bakcup I made....

Otherwise install fresh:
https://community.ui.com/questions/UniFi-Installation-Scripts-or-UniFi-Easy-Update-Script-or-UniFi-Lets-Encrypt-or-UniFi-Easy-Encrypt-/ccbc7530-dd61-40a7-82ec-22b17f027776

8 hours ago, Grobalt said:

is it possible to create / install lxc containers with the proxmox VE helper scripts ? on promox they run flawless but here on a "naked new lxc container" it seems they are not working:

Nope, but I've created such a container archive for testing purposes, do the following:

1. Open up a Unraid terminal and execute:

   wget -O /tmp/lxc_container_template.xml https://raw.githubusercontent.com/ich777/unraid-lxc-unifi/main/lxc_container_template.xml

2. In your Browser navigate to: http://<YourunRAIDIP>/LXCAddTemplate
3. Make your changes if necessary
4. Click Apply
5. Wait for the Done button

 

After that you should be greeted with that:

 

2 hours ago, bmartino1 said:

I have setup a crude way to acomplish the template...

Please ask before publishing such a complicated thing and also this complicated tutorial here:

(btw, LXC is not a VM and there is still no official support for LXC templates so you can't post it easily in a section here on the forums)

 

I've now already created a PR on your repository, this gives you (the LXC archive maintainer) basically the ability to do the following:

Open up a Unraid terminal and do the following:

1. git clone https://github.com/ich777/unraid_lxc_unifi
2. cd unraid_lxc_unifi
3. bash createLXCarchive.sh

This will basically do 1. pull the repository from GitHub, 2. change directory into the cloned repository, 3. call the createLXCarchive.sh which will create a temporary LXC container, execute the scripts one by one in the build directory output the archive, build.log and a md5 sum into your LXC base directory in the sub folder "/cache/build_cache".

 

After that you (as the maintainer) have to go to the GitHub repository, click on Releases, click on Draft a new Release, Choose or create a Tag, put in a Title and maybe short description and upload the three files from the build_cache directory and finally Publish the Release.

(this could be all automated but that's up to you and always depends on your environment)

(please keep in mind I didn't changed the repository links since you haven't accepted the PR)

 

If you want to give a user access to your archive just post something like that:

These are only five (or better speaking really only three) easy steps for a user to do until official support for container templates is introduced.

 

 

The huge benefit that a user gets from this is that he gets a similar experience to a Docker container and he doesn't have to fiddle around with any scripts:

 

 

Please always upload the build.log for full transparency and that users can review what was done when executing the createLXCarchive.sh

 

You can also see my other build scripts/examples for other containers here.

Thanks for your collaboration, that would be awesome if all promox helper scripts can be used an easy way soon!

23 minutes ago, Grobalt said:

Thanks for your collaboration, that would be awesome if all promox helper scripts can be used an easy way soon!

The Proxmox helper scripts won't work on Unraid since they are working completely different and not all necessary tools are available on Unraid however you should be able to install the Unifi Network Server as pointed out here (I really try to make this as simple as possible for the end user) :

 

ok ... would have been great in combination with the lxc updater etc

7 minutes ago, Grobalt said:

ok ... would have been great in combination with the lxc updater etc

What is the LXC updater?

 

The above linked container image has a script installed that check on every Sunday at 0:00 for Unifi updates and installs them if any are found.

it is one of the "base" scripts on the proxmox  helper scrips side:

 

https://tteck.github.io/Proxmox/

https://tteck.github.io/Proxmox/#proxmox-ve-cron-lxc-updater

 

This script will add/remove a crontab schedule that updates all LXCs every Sunday at midnight.

To exclude LXCs from updating, edit crontab (crontab -e) and add CTID as shown in the example (-s 103 111)

 

16 minutes ago, Grobalt said:

it is one of the "base" scripts on the proxmox  helper scrips side:

But that does the script in my container too.

Evey Sunday at 0:00

 

It always depends on how you set it up, I would not like to update all of my containers automatically too much risk involved there (Homeassistant, PiHole,...), actually that was one of the reasons why I switched Homeassistant over to a LXC container...

sure, but it is a "central" script and you have like a config file where you exclude the "not wanted" LXCs  all good 

Just now, Grobalt said:

sure, but it is a "central" script and you have like a config file where you exclude the "not wanted" LXCs  all good 

The main issue is that this thing is for Proxmox and as said above dependencies for these scripts are missing and the scripts are for Proxmox, that's why I came up with the container archive solution which should work more reliable (at least there will be always be a image available) and everything is self contained where you also should be able to transfer your containers over to other systems too.

 

But please be aware that the container that I made is just a proof of concept for @bmartino1 and I didn't actually tested it because I don't have any Unifi hardware and I'm not familiar with Unifi.

I can tell you that it works and you can reach the WebUI

11 hours ago, ich777 said:

Please ask before publishing such a complicated thing and also this complicated tutorial here:

(btw, LXC is not a VM and there is still no official support for LXC templates so you can't post it easily in a section here on the forums)

 

I've now already created a PR on your repository, this gives you (the LXC archive maintainer) basically the ability to do the following:

Open up a Unraid terminal and do the following:

1. git clone https://github.com/ich777/unraid_lxc_unifi
2. cd unraid_lxc_unifi
3. bash createLXCarchive.sh

This will basically do 1. pull the repository from GitHub, 2. change directory into the cloned repository, 3. call the createLXCarchive.sh which will create a temporary LXC container, execute the scripts one by one in the build directory output the archive, build.log and a md5 sum into your LXC base directory in the sub folder "/cache/build_cache".

 

After that you (as the maintainer) have to go to the GitHub repository, click on Releases, click on Draft a new Release, Choose or create a Tag, put in a Title and maybe short description and upload the three files from the build_cache directory and finally Publish the Release.

(this could be all automated but that's up to you and always depends on your environment)

(please keep in mind I didn't changed the repository links since you haven't accepted the PR)

 

If you want to give a user access to your archive just post something like that:

These are only five (or better speaking really only three) easy steps for a user to do until official support for container templates is introduced.

 

 

The huge benefit that a user gets from this is that he gets a similar experience to a Docker container and he doesn't have to fiddle around with any scripts:

 

 

Please always upload the build.log for full transparency and that users can review what was done when executing the createLXCarchive.sh

 

You can also see my other build scripts/examples for other containers here.

Thank You Very Much For this! I now understand how this works and why the repository is set up the way it is and how the codes / line would execute to build/make the LXC on unraid.

Just now, bmartino1 said:

Thank You Very Much For this! I now understand how this works and why the repository is set up the way it is and how the codes / line would execute to build/make the LXC on unraid.

I've also left a comment on GitHub, please don't change the temporary container name, this is a safety feature.

Please read the comment here.

Hey @ich777

How would one custom set a icon?



If i want to change the icon in the lxc tab where is that data loading from?

6 hours ago, bmartino1 said:

How would one custom set a icon?

Please read this post:

 

11 hours ago, ich777 said:

Please read this post:

 

Awesome. using a custom icon per the template, install made this folder.

Thank you. Just wasn't sure of the path.

lxc.lxcpath=/mnt/cache/appdata/lxddata/generallxcpath

9 minutes ago, bmartino1 said:

/mnt/cache/appdata/lxddata/generallxcpath

May I ask why you are using two folders for lxc …/lxddata/generallxcpath/…?

Something like: /mnt/cache/lxc in your case would be way simpler and I wouldn‘t recommend that you put the lxc directory in your appdata folder

No general reason.

its was how I originally setup pathing for the lxc settings, mainly for backup / general path

I my case, I want both under the same folder for custom rsync backup purposes.

General settings:


backup settings:

9 minutes ago, bmartino1 said:

I my case, I want both under the same folder for custom rsync backup purposes.

That makes not much sense for me since you backup the main data path and the backup path via rsync (at least how you described it since you backup your appdata directory).

 

I designed the Backup function in that way so that you can place it basically anywhere so that you don‘t have to do double the backups via rsync.

 

This was just for explanation, however you can do whatever you want just wanted to explain why it doesn‘t makes much sense to me.