Search results

You are correct. Using https://pve.proxmox.com/wiki/Unprivileged_LXC_containers to convert from privileged to unprivileged container. Though, if you have disabled login as any user including root with password and only allow certificate based logins should narrow safety down ;-)

You need to run in a privileged container. By default a LXC container is created unprivileged. See here: https://forum.proxmox.com/threads/docker-under-proxmox.81618/post-360134

Is it this you want? docker run -d \ --name nginx-proxy-manager \ -p 80:8080 \ -p 81:8181 \ -p 443:4443 \ -v /Docker/nginx-proxy-manager:/config \ jlesage/nginx-proxy-manager

I have read numerous times that people request support for Docker in Proxmox so I use some time yesterday to find a solution. The basis for the solution was this on Youtube: https://www.youtube.com/watch?v=79KiCBNbsbg I have tested his solution and it works great - I have decommissioned my home...

To me it sounds odd that you can give all permissions to a user/group but then again all != all. Why can root@pam not give any permissions to a user/group? This is contradictory to how permissions work in Linux/Unix.

Hi all, I have created a group named admins. This group has the following permissions: Path User/Group/API Token Role Propagate / @admins Administrator Yes I have assigned a user which login through ldap to this group. I have even...

These are just warnings and of no concern.

This package was pushed to stable yesterday: libpve-storage-perl (6.2-9) over (6.2-8) Maybe there is something in the patch(es) in libpve-storage-perl (6.2-9) which solves some or your problems?

Sounds reasonable. Thanks.

But now it is you Stoiko who is responding. I was actually trying to ask you a question on the pve-devel list: On Mon, 12 Oct 2020 17:34:56 +0200 Stoiko Ivanov <s.ivanov@proxmox.com> wrote: > This patchset follows the fix in > 609f117ff24d2cff6b155e1d4b1175ceebe5bd7b. Since several operations...

For privacy reasons I use my own email server. Also relaying through another email server pose some difficulties on me since it will be difficult to register a mail address to the pve-devel list not matching the the email servers domain ;-)

Hi all, When I try to send email to the pve-devel list by mail is returned with the following response: <pve-devel@lists.proxmox.com>: host firstgate.proxmox.com[212.224.123.68] said: 550 5.7.1 Service unavailable; client [83.93.223.153] blocked using zen.spamhaus.org (in reply to RCPT...

This is entirely up to the host to deside. write-back cache is equivalent to a hardware raid controller.

This is dangerous since writes are written to memory and first latter persisted to storage.

With statements like this it is also obviously that you are new to Linux ;-)

Maybe you should consider using restic on-top of rclone to enforce security? https://github.com/restic/restic

I can recommend this place for help with hardware raid controllers: https://kb.open-e.com/19/ There is many articles about various problems and recommended settings for optimal performance in different use cases.

Well, in my opinion virtualization requires thin provision and snapshots either from the image format or from the storage solution and abstraction from the hardware. You can live with one of the features missing if your not using it in an enterprise environment but missing two features is more...

It seems to lack snapshot feature? If this is the case then it is a very limited virtualization storage solution.

You could create a cron job to run pveum realm sync "Realm"