Search results

What about thermal limits? Anything restricted here?

That sounds pretty dangerous. So, it's probably best to configure the BIOS with some reasonable safety settings. Anyone knows which settings are most important?

I'm feeling with you. People are saying that Protectli have a very good customer service. That's actually why they are paying the premium price compared to all the other available boxes. Maybe you contact customer service and see if they have a solution? Or, if not, maybe they exchange the box...

How did the update work? You flashed the iso on a USB stick and booted from it? Did you need to do anything, like choosing the right entry in a Chinese menu? And did you need to reset the BIOS settings or set something special?

OK, I took the plunge and simply updated the system with the risk of getting an unbootable system. Fortunately, the system still works with a legacy boot (MBR + grub). Everything is alright. Puhh :)

Hello I have a Proxmox 6.4 ZFS installation on a HP Microserver Gen 8. I would like to update to 7.3, but I am afraid of the apparent requirement to move to proxmox-boot-tool using UEFI boot: If your system was installed on ZFS using legacy BIOS boot before the Proxmox VE 6.4 ISO...

Well, I started a couple of containers and so far, everything seems to work. docker always reports "overlayfs backed by ZFS". :)

Are these workarounds still needed for docker in an unprivileged container backed by ZFS? I just installed 7.3.3 on a new machine and created an LXC container. I loaded the overlayfs module on the host and configured docker in the container to use overlayfs2 driver. This is the output of...

P.S.: Did anyone test running a 5.4 kernel (from the Proxmox 6 series) on Proxmox 7.1 ? Maybe that could also be a viable way until there is a final solution?

As aufs cannot easily be compiled as a module (it needs several patches to the whole kernel), I gave up with compiling my own kernel module. I found a workaround, which would work, but which I not really like (using ext4 for the docker volumes). Therefore, I will downgrade back to Proxmox 6.4...

Are you sure about that? The proxmox kernel builds on top of ubuntu-impish. Looking at the kernel tree of the ubuntu-impish kernel 5.13, I do not see any aufs sources in the tree: https://kernel.ubuntu.com/git/ubuntu/ubuntu-impish.git/tree/fs To me that looks as if the fault is with ubuntu. I...

I stumbled over the same problem when upgrading my Proxmox 6 installation. I will now try to recompile the kennel to see if I get this working again.

The "userns-remap" option is in the lxc container (the docker host) in the /etc/docker/daemon.json file and does a complete user namespace remapping for all docker containers. So, in effect I have the following: a privileged lxc container with a docker host running as root, but confined by...

This I have. I also checked the ip_forward setting in all the ingress namespace. All of there are 1 (except on my RPI, where I needed to set this manually strangely...) My guess is that "lxc.mount.auto: proc:rw" and "lxc.apparmor.raw: mount," probably have a very similar effect, but I will give...

I just want to describe my experience with docker in lxc container under Proxmox. Maybe someone has some improvement ideas or my description is helpful for him/her. Goals: 1. Use the effortlessness of docker to install and maintain applications. 2. Monitor and manage centrally all running...

Yeah, that sounds resonable. Probably that's the cause. Would be great, if it thus is already fixed. I will update the host system and see, if it happens again. Although, the kernel oops was just a secondary effect. The primary effect was that the unpacking of a deb archive in the container...

Well, maybe I wasn't very clear here. The block was not just inside the container. The block stalled the whole host machine. So, there is, unfortunately, no chance to enter any commands when such a block may happen again. On the other hand, "By default the Proxmox containers do not account for...

Thanks for the feedback. This is really a serious problem as it did completely stall the whole machine. The LXC container has two vCPUs allocated and 1GB of RAM, which should be plenty for its normal processes (simple file server). At least as long as file caching etc is allocated to the host...

second part: Jan 5 09:14:08 proxmox kernel: [435636.005047] 175899 total pagecache pages Jan 5 09:14:08 proxmox kernel: [435636.005049] 2247 pages in swap cache Jan 5 09:14:08 proxmox kernel: [435636.005050] Swap cache stats: add 49884, delete 47637, find 441438/447781 Jan 5 09:14:08 proxmox...

After a hard reboot, this is what syslog has recorded: Jan 5 09:14:08 proxmox kernel: [435636.004894] SLUB: Unable to allocate memory on node -1 (gfp=0xd0) Jan 5 09:14:08 proxmox kernel: [435636.004899] cache: kmalloc-128(6:136), object size: 128, buffer size: 128, default order: 0, min...