Search results

I can't seem to setup a CT with this template. Is anyone else having an issue with this template? Where can I go to search for updated LXC templates I can upload? tar: ./var/spool/postfix/dev/urandom: Cannot mknod: Operation not permitted tar: ./var/spool/postfix/dev/random: Cannot mknod...

OK! Great! Sounds like it will go off without a glitch then.

I saw this guide: https://linuxconfig.org/how-to-upgrade-debian-8-jessie-to-debian-9-stretch that allows me to upgrade from jessie to stretch. I would assume I would need to do the same thing for proxmox to get from 4 to 5. Has anyone done it successfully? Any guides to do it?

I ended up doing a dist-upgrade on the box and that fixed this problem as well.

Not sure, but I did a dist-upgrade on the whole box and rebooted it and it fixed everthing.. Go figure.

After modifying /usr/share/perl5/PVE/LXC/Setup/Debian.pm do I need to restart something? Mine is still erroring with debian 9.

Job for pvedaemon.service failed. See 'systemctl status pvedaemon.service' and 'journalctl -xn' for details. dpkg: error processing package pve-manager (--unpack): subprocess installed post-installation script returned error exit status 1 E: Sub-process /usr/bin/dpkg returned an error code (1)...

It seems that /etc/lxc/default.conf doesn't have much bearing. /usr/share/lxc/config/common.conf seems to be a better fit except that you can't control it per container, it will be applied system wide to all containers. Would be nice if it could be controlled per container.

Gonna try throwing it into /etc/lxc/default.conf and seeing what happens.

It seems that the config files get regenerated by proxmox and overwrites the "lxc.rootfs.options = noatime" option I threw in there. How can I make it persistent?

Crap, when the config file gets regenerated, the parameter gets removed. Where can I make it part of the template and persistent.

I decided I wanted to test out how asterisk runs inside an lxc container. How latency is affected and what tweaks can be made to correct those problems. So I picked up a copy of freepbx and threw the ISO in the proper /var/lib/vz/template/iso directory and it showed up just fine. But when I...

This is better than sliced bread. I went from 12% Disk I/O utilization at non-peak hours to 00.01% at non-peak. Do not do this on your mail servers, as most use the last access times for archiving and other purposes.

I think I discovered in the LXC docs that ever since V1 you can add lxc.rootfs.options = noatime to /var/lib/lxc/100/config So I think I got this taken care of.

Since the /etc/fstab should not be edited in the Containers, I'm assume I can do this through one of the LXC config files. Does anyone know which ones I need to edit to add --noatime to the drive parameters. This should increase my IO performace, I hope.

I migrated an lxc container from Server A to Server B. On server A the container used quotas without a problem. On server B if I enable quotas the container fails to boot up and damages the image in a permanent way that if I turn off quotas it won't boot anymore. The only this that will fix the...

It would be nice if there was a warning on the proxmox installation screen that warns you of installing proxmox with ZFS over hardware raid(raid-5,etc). I'm assuming that this article applies to us as well as we are using ZFS for various partitions...

The repo is exactly like the one shown. I'm using the AT.DEBIAN repo instead of the US.DEBIAN. I think this line in the wiki is the issue: I think it really is a subscription key issue. I can make a screencast and upload it to youtube of the problem so that you can see that I'm following...

1. I installed from the latest ISO that its asking me to download, so that is unnecessary. 2. I checked the sources 3. I checked the REPO 4. I ran the update and dist-upgrade 5. I get nothing. The only thing I nothing is during the update I get: Err https://enterprise.proxmox.com...

Could it be that I do not have a subscription key?