Recent content by deang

I figured it out. When doing a "restore" of a CT, proxmox defaults to "non priviliged" when restoring the CT. In the restore dialog box you have to specifically uncheck "non priviliged" to get the CT to be restored as a priviliged CT like it was in the beginning.

I'm not entirely positive, but now that I think about it, I created this CT as "privileged". But after the restore, I *think* that it changed it to "non privileged" CT.

Hi, I have a proxmox v6 host. I made a backup of CT105 from the gui. Then I went to my container 105 (happens to be CentOS 7) and I did a yum update. But after the update I could no longer mount the NFS4 file system shares. It is an external NFS server called lurch not part of proxmox. Up...

I see now what the problem is. On my PVE host I didn't have the user "ceramext" in the /etc/passwd file. On my existing PVE host which is version 3, it wasn't necessary for the mapping to be passed to the CT. But with proxmox 6, looks like I do have to have all of the users in the /etc/passwd...

Thanks Republicus. I was missing no_root_squash from my NFS server's exports. I added it, refreshed everything and the problem persists. Here is my /etc/pve/storage.cfg dir: local path /var/lib/vz content iso,vztmpl,backup lvmthin: local-lvm thinpool data vgname...

I've posted a question to linuxquestions.org about a problem I'm having mapping IDs with NFS4 from a physical CentOs 6 NFS4 server and a proxmox CT CentOs 7 NFS4 client. I'm pretty certain this is NOT a proxmox issue, but figured I'd ask. My question is, is there any configuration on a proxmox...

What I did was recreate the container as privileged then under Options -> Features I can select/enable "Nesting" and "NFS"

I've been reading up on privileged containers. And now I'm wondering if I'd best not use a CT and AppArmor if this is considered as unsafe as mentioned in the section above. What I want are several guests, all using NFS to an external NFS server. Some guests using a lot of reads, some guests...

I want to have NFS client mount points within a CentOs 7 guest container. The NFS server is not on the proxmox host. The proxmox 6 host is able to mount these external NFS systems. The guest CT can ping the external NFS server. On the proxmox 6 gui, I go to the container where I want to mount...

Sorry, I'll post properly ....

I've installed a new proxmox 6 host. it resolves DNS fine. for a centos CT I selected to use the host's DNS. This created a good /etc/resolv.conf on the CT. But DNS is not resolving on the CT. I checked my host and it does have apparmor. So, I attempted to remove it and got this warning, not...

I haven't finished my work in post #3 but I'm still planning on making that move to serve samba shares directly from the proxmox server instead of a separate physical server. Here is that original link...

I went ahead and posted my problem to the Samba list. The answer I got back was that using NFS in the manner I was is considered "unreliable". I'll setup Samba on my proxmox server and deliver shares directly to the clients instead of using NFS. -- Dean

Hmmm, in edit mode that little mono spaced picture looks ok, but not in display mode.......

I apologize for cross posting this with LinuxQuestions.org. I posted there, but have not heard back. And now I'm wondering if I'm using an unsupported proxmox design. I have proxmox 5. And I'm using the underlying debian NFS export (not a VM or container). Then sending this to a separate...