There’s no requirement to use Bookworm to run Docker Aarch64 containers.
I demonstrated how to run Aarch64 containers some time ago.
Even if you upgrade from Bullseye to Bookworm you will still be running an armhf userland, so this won’t change anything there. You can still run aarch64 container on either platform regardless
You are more likely to get support on Bullseye than Bookworm.
Hi Sam. Practical question: does the Vero 5 ship from the UK exclusively? I’d be happy to upgrade but wondering whether I’ll have to steel myself for extra taxes and fees, etc. into the EU.
I don’t have a firm date on ending the offer, but it won’t last forever. If you want to purchase two Vero V in one order, just send an email to sales@osmc.tv and we will sort it out.
You’re not the only one. I bought my Vero 4K+ in December 2022 so I’ve only had two years of updates. I appreciate Sam wants to move on but that’s a long way from the five years of updates promised for those who, like me, purchased the device later on.
Understood. The five years were promised from the date of release, not from the date you purchased the product. This ended up as seven years for the 4K + and almost nine years for the 4K.
I will look at ways to make that clearer on the website.
We have also worked on upstreaming support for the Vero 4K and 4K + so that it lives on indefinitely, albeit not necessarily via OSMC. It has been supported by upstream / mainline Linux kernels for some time.
Hi @sam_nazarko ,
thanks for all the hard work. My device is still working quite well, so I’d hate it to see it unused because of discontinued support. Personally I have no problem with running old Kodi version, but my box is running SSH facing public internet and Samba on local network. I’m guessing all updates will be discontinued? The message on login shell feels like running apt to fetch new packages is a very bad idea:
Notice: This device is no longer officially supported as of 31/01/2025.
As a result, you will no longer receive officialy supported updates on this device.
You may wish to exercise caution using apt to perform upgrades.
For more information: please see https://osmc.news/QTupI
If no new security updates will be applied I guess, running SSH on public internet is no longer viable.
So I if pull new packages I’ll only get new packages from Debian (because OSMC is based on it), but this will not be supported by you. So if something breaks, it’s on me and help from forum right?
Is there any way of disabling the message that is shown when logging in via SSH?
If I’m logged in via SSH and want to edit something in /etc, I’d used to be able to type /e{tab}, but now I have to type /et{tab} due to the end_of_life_message file in /.