Actually not! My package is set to "Latest" - Always change this when creating a jail
1. I want my packages updated (when doing so the warning is issued)
The suggestion that was made was that you would be able to create FreeBSD 11.3 jails under 11.2-U7--and if you can do that, you can presumably also upgrade 11.2 jails to 11.3. Once that's done, you shouldn't get the warnings with either the ports or the packages. Here's what I said:Suggestions made was to wait for 11.2-U7 to get this resolved but clearly not resolved!
...or 11.2-U7, which Kris has said will allow the installation of a 11.3 jail, which might fix this problem.
I just updated to U7 and and was able to successfully upgrade one of my non critical jails to 11.3 release.The suggestion that was made was that you would be able to create FreeBSD 11.3 jails under 11.2-U7--and if you can do that, you can presumably also upgrade 11.2 jails to 11.3.
forumbackup1 successfully upgraded from 11.2-RELEASE-p8 to 11.3-RELEASE-p5!
Login as root and do.... iocage upgrade examplejail -r 11.3-RELEASEHow have you upgraded the Jail Release to 11.3?
Ok, Third attempt worked out what it seems - but I had to enter Y on like a 100 files and librariesAs earlier described - I ended up terminating the update process after seeing this prompt just hanging with a message of re-booting the system and then apply the update....
I since discovered that this message is bollocks, where giving it enough time it will complete the process successfully.
BUT(!), now Im stuck with my plex jail stuck on the previous jail version and when I try to do the update again I received this message...
Answered 'n' to the first prompt and the update failed - now I can't start the jail again - When trying to start it the message spat back said "Its already running" - even though the console thinks its down with NO option to stop it.
View attachment 34294
View attachment 34295
According to doco you can apply the update with the jail running or shutdown - either way.is it necessary to stop the jail or can it be done while it's running.
You've got some other issue going on. I've upgraded all my jails that are currently running from older versions and I've never been prompted to reboot the jail or the server.The jail update process would gain by adding something showing its still processing stuff instead of suggesting a reboot and separate update once back
Even though it looks like a prompt - its not! Its a misleading message where the process still is chugging along *but since it takes a long time its easy to think the process stalled - I also noticed that the path is misleading - the actual path where the ".../tmpnnnnn ends up is within the var/temp directory *and its automatically removed by the process*You've got some other issue going on. I've upgraded all my jails that are currently running from older versions and I've never been prompted to reboot the jail or the server.