On 7/11/19 11:45 AM, Vasily Averin wrote:
> Dear Hristo,
> if I remember correctly,  osrelease.conf-related machinery recognized 
> container's type by its template.
> I.e. if you need to adjust osrelease "3.20.0" in some container, you need to 
> specify proper IS template in its config file 

here is example from my test node,
uname inside fedora-27 -based container was adjusted based on content of 
osrelease.conf

[root@vvs-ovz6 ~]# uname -a
Linux vvs-ovz6.sw.ru 2.6.32-042stab132.1.vvs.psbm87155v12 #1 SMP Mon Aug 13 
19:28:24 MSK 2018 x86_64 x86_64 x86_64 GNU/Linux

[root@vvs-ovz6 ~]# grep TEMPLATE /etc/vz/conf/177.conf 
OSTEMPLATE="fedora-27-x86_64-20171116"

[root@vvs-ovz6 ~]# grep fedora-27 /etc/vz/osrelease.conf 
fedora-27       4.14.0

[root@vvs-ovz6 ~]# vzctl exec 177 uname -a
Linux vvs-ovz6.sw.ru 4.14.0-042stab132.1.vvs.psbm87155v12 #1 SMP Mon Aug 13 
19:28:24 MSK 2018 x86_64 x86_64 x86_64 GNU/Linux

> https://src.openvz.org/projects/OVZL/repos/vzctl/browse/etc/osrelease.conf
> 
> # List of kernel versions (osreleases) required by different
> # distributions (OS templates). vzctl tells kernel to report
> # the given version to containers based on a specified distro.
> #
> # Format: <template> <minimum kernel version required>
> ...
> suse-13.2     3.16.6
> 
> 
> On 7/11/19 1:54 AM, Hristo Benev wrote:
>> Hi,
>>
>>
>> as usual with the release on new debian version there is the issue with libc 
>> refusing to install on older kernel.
>>
>>
>>  cat /etc/debian_version
>> 10.0
>>
>>
>> cat /proc/sys/kernel/virt_osrelease
>> 2.6.32-042stab139.1
>>
>>
>> in
>>  /etc/vz/osrelease.conf
>> I have
>> debian-8.0      3.20.0
>> debian-9.0      3.20.0
>> debian-10.0     3.20.0
>>
>>
>> any idea how to fix it?
>>
>> _______________________________________________
>> Users mailing list
>> Users@openvz.org
>> https://lists.openvz.org/mailman/listinfo/users
>>
_______________________________________________
Users mailing list
Users@openvz.org
https://lists.openvz.org/mailman/listinfo/users

Reply via email to