Recent content by maeries

  1. M

    [SOLVED] VM Harddrive passthrough: VM and host are not in sync

    That was also my first guess, but since none of the like five tutorials I read mentions it, I tought it is fine Do you mean running sudo qm set 105 -virtio2 /dev/sdb1 or are you talking abount something different?
  2. M

    [SOLVED] VM Harddrive passthrough: VM and host are not in sync

    it may be a bad title, but I don't know how else to describe it. So I have a Ubuntu Server VM on Proxmox and I want to passthrough some drives (as passing through a directory does nto work afaik). I used sudo qm set 105 -scsi2 /dev/sdb1 to do so. I then mounted it in the guest by putting...
  3. M

    Passing a Physical Drive through to a VM in ProxMox

    But then why would there be a virtio option in the first place?
  4. M

    Priviledge Container: disabling apparmor does not work

    Also what I found and what might lead to a better solution is that $ sudo aa-status apparmor module is loaded. 17 profiles are loaded. 17 profiles are in enforce mode. /usr/bin/lxc-start /usr/bin/man /usr/lib/cups/backend/cups-pdf /usr/sbin/cups-browsed /usr/sbin/cupsd...
  5. M

    Priviledge Container: disabling apparmor does not work

    Found a solution. Run docker with --security-opt apparmor:unconfined respectively put security_opt: - apparmor:unconfined as in services: pihole: container_name: pihole image: pihole/pihole:latest security_opt: - apparmor:unconfined in your docker-compose.yml
  6. M

    Priviledge Container: disabling apparmor does not work

    Same problem here though with a bit different behaviour. With apparmor installed I get: $ docker-compose up -d Building with native build. Learn about native build in Compose here: https://docs.docker.com/go/compose-native-build/ Starting pihole ... error ERROR: for pihole Cannot start...
  7. M

    Make Google Drive accessible in an LXC: Best practices?

    Have you set the --allow-other option in rclone?
  8. M

    Apparmor permission issues after switching from unprivileged to privileged LXC

    No. I guess the problem is that Apparmor does not have the right profile installed, but I have no idea where to get it and how to use it, if profiles are the problem at all
  9. M

    Apparmor permission issues after switching from unprivileged to privileged LXC

    Everything works when Apparmor is not installed. But Apparmor is a security feature and I would like my server as secure as possible
  10. M

    Apparmor permission issues after switching from unprivileged to privileged LXC

    Plot twist! The solution I posted above does NOT solve the problem. I now switched a second server from unprivileged to privileged by what I noticed that uninstalling apparmor inside the LXC solved the problem. Now I don't really know what apparmor does, but I guess one wants to have it...
  11. M

    [SOLVED] Why is the 'data' LV much smaller that the disc?

    Thanks. Guess I have to research the what static and thin means to fully understand your answer
  12. M

    [SOLVED] Why is the 'data' LV much smaller that the disc?

    I apologize if this is a noob question. So I installed Proxmox "normally", i.e. with LVM and ext4 some time ago. Now i noticed that my SSD shows up with 223,57GiB in size under Datacenter->pve->Disks. But under Datacenter->pve->Disks->LVM-Thin the data LV is just 141,43GiB. What is the rest used...
  13. M

    Apparmor permission issues after switching from unprivileged to privileged LXC

    lol, one more google search solved the problem. https://forum.proxmox.com/threads/5-3-and-lxc-nesting.49951/post-232938
  14. M

    Apparmor permission issues after switching from unprivileged to privileged LXC

    I was running an unprivileged LXC and converted it to a privileged one (backed it up and then restored with it set to privileged) and now I have issues with Apparmor. My main problem is starting a Docker container ~/pihole$ docker-compose up Creating network "pihole_default" with the default...