Search results

  1. lxc with docker have issues on proxmox 7 (aufs failed: driver not supported)

    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?
  2. lxc with docker have issues on proxmox 7 (aufs failed: driver not supported)

    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...
  3. lxc with docker have issues on proxmox 7 (aufs failed: driver not supported)

    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...
  4. lxc with docker have issues on proxmox 7 (aufs failed: driver not supported)

    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.
  5. Another docker experience on Proxmox

    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...
  6. Another docker experience on Proxmox

    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...
  7. Another docker experience on Proxmox

    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...
  8. abysmal write performance on ZFS lxc container? (now with kernel oops)

    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...
  9. abysmal write performance on ZFS lxc container? (now with kernel oops)

    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...
  10. abysmal write performance on ZFS lxc container? (now with kernel oops)

    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...
  11. abysmal write performance on ZFS lxc container? (now with kernel oops)

    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...
  12. abysmal write performance on ZFS lxc container? (now with kernel oops)

    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...
  13. abysmal write performance on ZFS lxc container? (now with kernel oops)

    Ooops, a few minutes later I even get memory allocation failures! Not good. Complete kernel oops. "SLUB: Unable to allocate memory on node -1" and "Possible memory allocation deadlock". System is hanging (100% CPU usage). I guess, I need to pull the plug. Before that happened about 4,3 GB RAM...
  14. abysmal write performance on ZFS lxc container? (now with kernel oops)

    Hello I installed 4.1 on a hp microserver with 12GB RAM and a 3TB HDD. I mainly use lxc containers and added a local ZFS storage for these. I noticed extremely bad write performance for these containers. This morning I installed webmin on a debian container. The dpkg install process of the one...

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get your own in 60 seconds.

Buy now!