Hey guys just to let you know, the FreeBSD images for the public cloud are utterly broken, basically OVH has shoved in binaries from a different version of freebsd and not upgraded correctly, meaning both ports and pkg's will not work.
The fix for this is to buildworld for 10.1 https://www.freebsd.org/doc/handbook/makeworld.html and then installing that, afterwards sync the sources for 11.4 and build/install that make sure to follow all normal upgrade steps, mergemaster etc...
Then you could continue with 11.4 or upgrade to 12.1 (which is the current release)
OVH Cloud - FreeBSD is utterly broken and running an EOL version (10.1)
Related questions
- Can i use my own public cloud vm with floating ip as internet gatewaway for my private network?
12892 
26.01.2026 08:13
- IPv6 subnet/extra IPv6 IPs on cloud instances/VPS
11101 31.01.2018 07:31
- Problem with Windows Server 2019 activation
10614 30.12.2020 04:04
- Is the Plesk License included?
10169 02.01.2018 11:56
- Ubuntu 20.04 image in OVH has been marked as DEPECRATED
9172 04.12.2020 23:28
- Automatic Block storage backup - how?
8325 06.05.2020 17:31
- Private Network shared between two or more Public Cloud projects
7684 11.03.2021 13:19
- Setup clickhouse with s3 high performance storage class (express onezone)
7602 16.10.2025 13:28
- Orders for Public Cloud project get cancelled
6978 02.07.2025 16:06
- Error has occurred creating your Public Cloud project
6794 08.10.2021 08:52
You can test this by creating a sandbox FreeBSD box and yes well ... trying to install anything :)
Note to OVH: If you are unsure how to actually get a correctly built freebsd image, drop me a message I would happily put one together for you
hello
anyone here ?
Hey there, it is usually better to simply ask a question :)
As it turns out you can actually get out of this little problem with freebsd-update -r 12.1-RELEASE upgrade ... however build world will fail without creating a fake swap using mdconfig -a -t vnode (2G does it) - this is for the smallest sandbox
As for fixing package you can fix it by force installing pkg from the freebsd 10.1 package repository and forcing it to re-initilize, though that obviously does not get rid of the problem the entire OS is effectively EOL for 10.1
Nice to know someone is watching the FreeBSD builds, have you checked Ubuntu 20.04 yet?