TrueNAS 25.04-BETA.1 is Now Available!

[Stux]

@Brezlord

I thought that there would macvlan in the GUI this release for Docker apps

No. You should be able to IP bind existing IP aliases in apps.

Vote here for Macvlan support for apps:

Allow apps to have their own IP

Problem/Justification Add ability to use separate IPs on apps in Electric Eel. With GUI manageability. Impact It will be similar to a CORE jail. User Story I don’t think this needs much of a story. It’s very practical to have apps using their own network stack.

Vote here for Macvlan support for TrueNAS itself:

Add support for creating MACVLAN interfaces with "Add Interface"

TrueNAS should support creating and configuring a MACVLAN interface when using “Add Interface”. Ie, MACVLAN should be an option in this menu. [Screenshot 2024-11-27 at 3.38.13 PM] This would prevent complicated CLI scripting in order to create macvlan interfaces and configuring routing tables to allow docker macvlan<->host communication. Macvlan is supported by the Linux kernel and is a well known Linux network type It behaves a bit like a cross between a VLAN and a Bridge. The underlying…

[SmallBarky]

If you find a bug, use Report a Bug. Smile icon on upper right of GUI for giving feedback and reporting bugs.

[Brezlord]

Sorry should have added that someone has created a bug for it [NAS-134215] Cpu temperature widget no longer works - iXsystems TrueNAS Jira

[Brezlord]

Voted x 2. There is not option in the GUI that I can see to bind an app to an alias IP. I have look around in the Plex config.

[nasbdh9]

Do need an enterprise license to use RDMA function?

[SmallBarky]

@eturgeon

• NFS over RDMA support - Enterprise Feature (NAS-131784).
• iSCSI Extensions for RDMA (iSER) support - Enterprise Feature (NAS-106190).

They are listed ‘Enterprise’ in first post above.

[jasmeralia]

Upgraded with zero issues.

[Stux]

For those attempting to port a VM to fangtooth, you can hard code the MAC address of an interface on a VM with the following incus incantation:

incus config device set <vm name> <eth device> hwaddr=<mac address>

Are there any plans to expose the ability to set the MAC address in the GUI before release?

This is needed if people are expecting to use the same DHCP allocations after manually migrating their VMs.

What about PCIe pass-through?

For those who would like to dump your old configs after upgrading to fangtooth, you can still run the following query in the shell

midclt call vm.query | jq

[priezz]

@LarsR

Has anyone tried to migrate their apps from jailmaker to incus lxc and can answer how gpu passhtrough works? I’m kind of hesitant to try the beta because i don’t have a system to play around with.

I did not try to migrate, but jailmaker keeps working, so there is no rush. Proxmox installed in nspawn (jailmaker) unsurprisingly keeps working well.

[priezz]

I have migrated 2 days ago with no issues, everything is working well. Just tried Incus clustering - seems to work. Question to the team - are there any plans to add clustering staff into the TrueNAS UI?

For those who would like to have Incus UI from Canonical here is the instruction (assuming that your pool is mounted at ‘/mnt/data’):

# SSH into your NAS

POOL_MOUNT='/mnt/data'

# Install Homebrew
wget https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh
bash install.sh
rm install.sh
sudo mv /home/linuxbrew/.linuxbrew "$POOL_MOUNT/"
sudo ln -s "$POOL_MOUNT/.linuxbrew" /home/linuxbrew/
sudo mkdir "$POOL_MOUNT/.tmp"
sudo chown $(whoami): "$POOL_MOUNT/.tmp"
echo "eval \"\$(/home/linuxbrew/.linuxbrew/bin/brew shellenv)\"" >> ~/.zshrc
echo "export HOMEBREW_TEMP=\"$POOL_MOUNT/.tmp\"" >> ~/.zshrc
eval "$(/home/linuxbrew/.linuxbrew/bin/brew shellenv)"
export HOMEBREW_TEMP="$POOL_MOUNT/.tmp"

# Install Yarn
brew install node yarn

# Build and install Incus UI
cd "$POOL_MOUNT/.tmp"
git clone https://github.com/zabbly/incus-ui-canonical.git
cd incus-ui-canonical
yarn
yarn build
sudo mv build/ui "$POOL_MOUNT/.incus-ui"
cd ..
rm -rf incus-ui-canonical
sudo mkdir /etc/systemd/system/incus.service.d
echo "[Service]\nEnvironment=INCUS_UI=$POOL_MOUNT/.incus-ui" | sudo tee /etc/systemd/system/incus.service.d/ui.conf

# Activate external HTTPS access to Incus
sudo incus config set core.https_address <NAS_IP>:8443

# Reload Incus service
sudo systemctl daemon-reload
sudo systemctl restart incus

# From your local machine:
#
# 1. Open https://<NAS_IP>:8443 with your browser
# 2. Click "Create a ew certificate"
# 3. Click "Generate"
# 4. Enter a password for the new certificate
# 5. Download .crt and .pfx files, e.g. to ~/Downloads
# 6. Copy .crt to your NAS (run from your local machine) 
#    scp ~/Downloads/incus-ui.crt <ADMIN>@<NAS_IP>:~
# 7. Follow instructions to import .pfx into your browser

# Import the certificate to Incus
sudo incus config trust add-certificate ~/incus-ui.crt

# Done

[returnofblank]

The new Instances feature seems to use port 53 for dnsmasq.

This causes problems for apps that also use port 53 like Pihole.

Normally not an issue, since you can place them on separate interfaces (e.g. Incus on a virtual interface), but Pihole listens on all interfaces (and I haven’t found a way to limit it to one). That means the only way to get around this is to change the port for Incus’s dnsmasq, which I also haven’t found a way to do either.

[Flo]

@returnofblank

Pihole listens on all interfaces (and I haven’t found a way to limit it to one)

Pihole has a setting to choose which interfaces it listens on. Otherwise I use AdGuard Home and there you can choose the interface during installation.
https://docs.pi-hole.net/ftldns/interfaces/

[Captain_Morgan]

@Stux

Are there any plans to expose the ability to set the MAC address in the GUI before release?

Not that I can see…

I’d suggest reporting it as a bug… if not possible in remaining time, it might become a feature request later.

[dasunsrule32]

More stable than I was expecting… Even the old jailmaker is working properly now. Thank you!

As others mentioned, CPU gauge doesn’t work.

I will start playing with Nvidia in Incus and see where I get as I migrate away from jailmaker to Incus.

I also think that the option to install Nvidia Drivers should be moved under the advanced GPU settings though and not be located under applications. It’s an odd place to put it currently.

[Stux]

Upgraded my potato system to Fangtooth Beta-1.

I think it may have more memory free than EE did

[Stux]

Vote for this Feature Request to improve the Browse Images catalog pane

Allow including "Aliases" when browsing and searching Incus Images catalog

Its a general issue, which is solved in incus via “Aliases” For example, Debian has the same issue [Screenshot 2025-02-18 at 1.53.51 PM] Where as here’s the command line version, with alias display enabled # incus image list -c Lfpdasu images:debian architecture=x86_64 +-------------------------------+--------------+--------+----------------------------------------+--------------+-----------+----------------------+ | ALIASES | FINGERPRINT | PUBLIC | DESC…

[dasunsrule32]

You got more TB’s than I do on your potato! I only have 3.5TB usable! I can’t afford more hard drives right now either to dedicate to media… ala Plex, ereader, and Immich.

[dasunsrule32]

Updooted

[Stux]

@TheJulianJES

I’ve not used Incus/LXC before, so it’s not obvious to me what the 10 GiB disk is also needed for in VMs?

By default, when setting up a VM, incus creates a 10GB sparse zvol as the root disk/device, and then it would populate that from an image in the catalog

I suspect the existing zvol is then being attached to the VM as a secondary device… to avoid having to “import” it into Incus’ storage pool

Which you can then boot from.

I’m not sure if there is any simple way to skip the root device attachment, although as its a sparse zvol it should be using very little space.

I’d be concerned that VM “snapshots” etc won’t know about the secondary zvol.

[Captain_Morgan]

Its the same problem with a server with a boot device and then using shared storage for its data.

The usual approach is to make sure the boot device is not used for active data… only for software.