Related posts https://forum.proxmox.com/threads/systemd-and-debian-jessie-template.29739/ and https://forum.proxmox.com/threads/use-systemd-in-debian-containers.26979/#post-151726
Following you reply, I have retested. Indeed it works in a privileged container, but it fails with an unprivileged container.
Btw, did you upgrade from 8.4 to 8.6 ? I didn't see any apt-get dist-upgrade
RATIONALE
The default proxmox debian 8 template, debian-8.0-standard_8.4-1_amd64.tar.gz 20-Apr-2016 12:16, from http://download.proxmox.com/images/system/ , ships with sysv.
(See “If I remember correctly, there is a problem with nested systemd. Therefore the Debian 8 template ships with...
I am sure I did it the right way ( disable pve-no-subscription and enable enterprise). First after enabling, I got Failed to fetch https://enterprise.proxmox.com/debian/dists/jessie/pve-enterprise/binary-amd64/Packages HttpError401, but in 15 min everything was ok ( works as designed).
The zfs...
Why do I use no subscription in the first place? For zfs custom partitions.
Martin Maurer replied in a ticket to my question : After buying PVE subscription, can I enable during custom install?
Quoting: "If you do not use the ISO, the way is to use the pve-no-subscription packages to get the...
Thanks for reply. For an unprivileged container, how to I raise the limit ? Or is inhereted from host machine?
$ sudo vi /etc/security/limits.conf
lxcd soft nofile 1024
lxcd hard nofile 8192
doesn't work!
I have noticed also...
1) Ssh into the container: ulimit -n 1024
2) Console encrypted vnc via proxmox web interface: ulimit -n 1024
2) From host / pct enter ContainerID : ulimit -n 65536
What is the real ulimit value for lxc containers? Is inhereted from the host?
If I want to increase the value, should I apply...
Thanks for reply.
Of course, no one can guarantee. Since host system is Debian8 with Ubuntu based kernel, I should be always safe if my container OS is Debian8 , keeping the system uptodate.
But if my customer chooses Centos6 container ?
Let's take this use case. In your environment, do...
If you really want to go with lvm, add with noauto option in /etc/fstab
/dev/mapper/pve-root / ext4 defaults,noauto 1 2
Afterwards, chmod +x /etc/rc.d/rc.local and add the following lines to /etc/rc.local
vgchange -a y
mount /dev/mapper/pve-root
In rescue mode, edit /etc/default/grub and add
GRUB_CMDLINE_LINUX=" rootdelay=15"
Run update-grub and reboot
I ran into this issue after custom install https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Jessie ( Proxmox on top of Debian8 ).
On the other hand, looking into OVH default...
OVH response: "The issue has been fixed for the new reinstallation.
So, you can reinstall the server or you use this workaround solution:
rm -rf /var/lib/lxcfs/* && systemctl restart lxcfs"
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.