@fiona
Is it possible that you activate voting for your Bugzilla bugtracking system?
Then you could vote up enhancement proposals and you see which ones are most wanted by the users.
It would be good to have ntfy.sh as notification service available as well.
Ntfy.sh is similar to Gotify which is already implemented in Proxmox.
If you are going to add it, then please also add options to allow a basic authentication, since ntfy.sh itself has no user/password authentication...
I did setup domain1 in Configuration-> Other-> WebAuthn TFA and added a WebAuthn authentication to the user.
The user was able to login.
Then I changed over to domain2 and logged in with TOTP.
I did change to domain2 in Configuration-> Other-> WebAuthn TFA and added another WebAuthn...
I noticed that I can setup in Configuration-> Other-> WebAuthn TFA just one domain, but I have multiple domains (separate domains, not sub domains) accessing this server.
How can I setup WebAuthn for multiple domains?
I had the same issue today when I tried to rename a node.
It was very strange, the file /etc/pve/lxc/101.conf did not exist anymore and I was also not able to create one (error: file already exists).
In the end I changed the name back how it was before and did a reboot to get the server back...
I had the situation yesterday.
It ended up with a corrupt filesystem in the LXC and I had to reinstall the LXC.
I expected that in this case the containers just cannot write to the disk anymore, but not such a desaster.
Is this the way how it should be by its design that the filesystem could...
Is there actually a benefit if you pass the whole controller through to the VM compared to just the disk?
Do I have to expect then a better performance or maybe a better SMART support?
Right now i have passed through the disk to TrueNAS scale, but it looks SMART is not working for it:
This fixed the issue with the user and group ownership:
Show current ownership of directoy:
root@pve1:/var/lib/lxc/110/rootfs# ls -ln
total 92
drwxr-xr-x 2 100000 100000 4096 Aug 6 11:10 bin
drwxr-xr-x 2 100000 100000 4096 May 13 2019 boot
drwxr-xr-x 2 100000 100000 4096 Dec 10 2008...
To run
root@pve1:/var/lib/lxc/110/rootfs/var/log# chown 100000 *
on these directory fix that and the backup is working now, thank you very much Fabian.
root@pve1:/var/lib/lxc/110/rootfs/var/log# ls -ln
total 86500
-rw-r--r-- 1 100000 100000 0 Mar 1 2021 alternatives.log
-rw-r--r-- 1...
You mean like this?
root@pve1:~# pct mount 110
mounted CT 110 in '/var/lib/lxc/110/rootfs'
root@pve1:/var/lib/lxc/110/rootfs# ls -ln \
./var/log/btmp \
./var/log/mail.err \
./var/log/kern.log
-rw-rw---- 1 0 43 2688 Feb 27 2021 ./var/log/btmp
-rw-r----- 1 0 4 6482 Feb 27 2021...
I think I am having the same issue, I end up in an error when I try to run a backup:
INFO: starting new backup job: vzdump 110 --notes-template '{{guestname}}' --remove 0 --mode stop --storage local --compress zstd --node pve1
INFO: Starting Backup of VM 110 (lxc)
INFO: Backup started at...
I am getting this error if I try to start my mailserver docker container.
Starting mail ... error
ERROR: for mail Cannot start service mail: b'OCI runtime create failed: container_linux.go:349: starting container process caused "process_linux.go:449: container init caused \\"write sysctl key...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.