You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
I installed proxmox-nixos without troubles on my nixos.
However, I am using impermanence.
I added these directories to be persistent:
environment.persistence."/persistent".directories=["/var/lib/vz""/var/lib/pve-cluster""/var/lib/pve-firewall""/var/lib/pve-manager"{directory="/etc/pve";# user = "root";# group = "www-data";}];
The problem is that /etc/pve is a directory controller by fuse where even the root user cannot delete everything's
I tried to add programs.fuse.userAllowOther = true; to my config as mentioned by the impermanence doc, but this seems not to be enough.
(it seems applied correctly /dev/fuse on /etc/pve type fuse (rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other)
May it be possible to simply change the folder where proxmox saves its data?
Having this directory as a parameter would be pretty simple for impermanence user to move to their non formatted directory without fighting with fuse access.
The text was updated successfully, but these errors were encountered:
Hi,
I installed proxmox-nixos without troubles on my nixos.
However, I am using impermanence.
I added these directories to be persistent:
The problem is that
/etc/pve
is a directory controller by fuse where even the root user cannot delete everything'sI tried to add
programs.fuse.userAllowOther = true;
to my config as mentioned by the impermanence doc, but this seems not to be enough.(it seems applied correctly
/dev/fuse on /etc/pve type fuse (rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other
)May it be possible to simply change the folder where proxmox saves its data?
Having this directory as a parameter would be pretty simple for impermanence user to move to their non formatted directory without fighting with fuse access.
The text was updated successfully, but these errors were encountered: