Can't start jails/plugins on 11.2BETA1: iocage error

[corv]

I've got a fresh install of 11.2BETA1 (with a config file).

After creating a jail/plugin it refuses to start up on the second boot.

Digging into console reveals that iocage complains
iocage start testjail

Code:

Host: 11.1 is not greater than jail: 11.2

Technically iocage isn't wrong...
uname -a

Code:

FreeBSD scrubbed_hostname 11.1-STABLE FreeBSD 11.1-STABLE #0 r325575+b31fa24ea5b(freenas/11-stable): Thu Jul  5 16:57:13 EDT 2018	 root@nemesis.tn.ixsystems.com:/freenas-11.2-releng/freenas/_BE/objs/freenas-11.2-releng/freenas/_BE/os/sys/FreeNAS.amd64  amd64

 

[dlavigne]

This has been fixed for BETA2.

 

[LawrenceSystems]

Bug report here https://redmine.ixsystems.com/issues/36598

 

[corv]

Thank you. Is there a workaround for the time being?

 

[SavageAUS]

Hope I'm not hijacking this thread as I thought I would tack this on here.

Is it best practice as of 11.2 to use the plugin system or manually create an iocage jail?
Will iocage networking be fixed in beta 2?

 

[corv]

Hope I'm not hijacking this thread as I thought I would tack this on here.

Is it best practice as of 11.2 to use the plugin system or manually create an iocage jail?
Will iocage networking be fixed in beta 2?

With regards to iocage networking, have you also run into the issue where using DHCP for plugins won’t work?

As for your question, I noticed that modifying a plugin from iocage will remove it from the Plugins list and only list it as a jail, otherwise I haven’t seen any difference between the two. Maybe updates are handled differently?

 

[Jorsher]

I also have this problem. Jails worked the first time. Stopped working on reboot, with the same reason in console.

Is there a workaround?

 

[8-bit Yoda]

Is there a workaround?

Edit the jail's config file /mnt/iocage/jails/<your_jail>/config.json
Find the entry that says "release": "11.2-RELEASE", and change the 11.2 to 11.1.

Make a note to change it back to 11.2 whenever you upgrade your host system to 11.2

 

[Jorsher]

Thanks, I had hope it was as easy as lying. I'm on 11.2BETA1 that's why I'm annoyed it doesn't label the OS as 11.2.

 

[28061]

Edit the jail's config file /mnt/iocage/jails/<your_jail>/config.json
Find the entry that says "release": "11.2-RELEASE", and change the 11.2 to 11.1.

Make a note to change it back to 11.2 whenever you upgrade your host system to 11.2

How do I do this? I've tried to create a share mounting the iocage pool to navigate but it doesn't work, tells me that "The path must reside within a volume mount point".

Can I navigate and edit using the console? If so, would you mind explaining how? Thank you.

EDIT: Sorted it - thank you very much.

 

[AVSION]

Thank you. Is there a workaround for the time being?

workaround i used

Code:

iocage console jailname

to start my jail worked for me on 11.2 release

 

[corv]

workaround i used

Code:

iocage console jailname

to start my jail worked for me on 11.2 release

Maybe it's been fixed within the plugin download then but I still had to use the workaround 8-bit Yoda suggested earlier.

Thanks for the heads up!

 

[corv]

It's fixed in 11.2-BETA2 which was released Aug 1st.

 

[28061]

It's fixed in 11.2-BETA2 which was released Aug 1st.

Still doesn't work for me using Beta2, and the bug report says it's due for fix in BETA3.

EDIT: Apologies - I'm confusing two different bugs.