airflow
Contributor
- Joined
- May 29, 2014
- Messages
- 111
Hi,
I create my jails typically automatized via iocage-commands in scripts/commandline:
This works fine and these jails can then also be managed via FreeNAS GUI. Since the latest update of FreeNAS to FreeNAS-11.2-U6, it is possible to chose 11.3 as the release for a new jail in the GUI. But when i modify my command to reflect that, it results in the following error:
I understand that this is not supported while the host of the system is still on 11.2. But why is it possible via the GUI?
Actually, when I check the version with "uname" from within 11.3-jail (which has been created via GUI and is displayed in the GUI as 11.3), it still shows 11.2:
Is this a bug in the GUI?
Regards,
airflow
I create my jails typically automatized via iocage-commands in scripts/commandline:
Code:
iocage create -n testus ip4_addr="vnet0|192.168.0.36/24" defaultrouter="192.168.0.1" allow_raw_sockets="1" vnet=on bpf=yes boot=on -r 11.2-RELEASE
This works fine and these jails can then also be managed via FreeNAS GUI. Since the latest update of FreeNAS to FreeNAS-11.2-U6, it is possible to chose 11.3 as the release for a new jail in the GUI. But when i modify my command to reflect that, it results in the following error:
Code:
$ iocage create -n testus ip4_addr="vnet0|192.168.0.36/24" defaultrouter="192.168.0.1" allow_raw_sockets="1" vnet=on bpf=yes boot=on -r 11.3-RELEASE Host: 11.2-RELEASE is not greater than target: 11.3-RELEASE This is unsupported.
I understand that this is not supported while the host of the system is still on 11.2. But why is it possible via the GUI?
Actually, when I check the version with "uname" from within 11.3-jail (which has been created via GUI and is displayed in the GUI as 11.3), it still shows 11.2:
Code:
root@testus-dhcp:~ # uname -a FreeBSD testus-dhcp 11.2-STABLE FreeBSD 11.2-STABLE #0 r325575+5920981193f(HEAD): Mon Sep 16 23:00:13 UTC 2019 root@nemesis:/freenas-releng/freenas/_BE/objs/freenas-releng/freenas/_BE/os/sys/FreeNAS.amd64 amd64
Is this a bug in the GUI?
Regards,
airflow