Jail trouble on 11.0-STABLE

[Nasb Klamb]

I updated my host to the FreeNAS-11-STABLE train (maybe not a good idea?). Now when I create a jail and attempt to build from the portsnap tree, I get complaints like "Ports Collection support for your FreeBSD version has ended, and no ports are guaranteed to build on this system. Please upgrade to a supported release."

When I do a "freebsd-version" inside the jail, it reports "11.0-RELEASE-p1"

When I do it within the host, it reports "11.0-STABLE"

I don't know what to do. Any advice would be very welcome.

Thanks!

 

[dlavigne]

See https://forums.freenas.org/index.ph...to-eol-jails-in-freenas-11.59574/#post-422130.

 

[Nasb Klamb]

See https://forums.freenas.org/index.ph...to-eol-jails-in-freenas-11.59574/#post-422130.

Thanks for the link. I will see what 11.1 brings, but I'm hoping that it fixes problems that still exist once I set the unsupported system variable. I tried, e.g. to build apache24 and it fails because it expects a slightly older version of perl5 than is on the system. And that isn't the only version issue.

 

[Joe Fenton]

So do I understand correctly, that if we have 11.0-RELEASE-p1 jails, and 11.1-STABLE freenas OS, if you want to update the jails, you have to recreate them?

 

[Jailer]

So do I understand correctly, that if we have 11.0-RELEASE-p1 jails, and 11.1-STABLE freenas OS, if you want to update the jails, you have to recreate them?

Depends. If it is a warden based jail (old UI), yes. If it's an iocage based jail (newUI or CLI), no.

 

[Joe Fenton]

If the old UI is the one that's a bit clunky and slow (loading the side bar for example), then I'm using that :(. I found the new UI seemed to be missing things, so went back to the old one, plus most of my jails were created before the new UI came along anyway. That's a bit annoying, going forward, if I want to update. What's the easiest way to migrate data/setup over to newly created jails?