Search results

@0C0C0C Not really a PVE problem, more related to container security. You can use systemd overrides in a clean manner (example for Dovecot): # cat /etc/systemd/system/dovecot.service.d/PrivateTmp.conf [Service] PrivateTmp=false ProtectSystem=false PrivateDevices=false # systemctl...

So far everything works fine for my upgraded single node. Will get hands on a brandnew AMD Eypc Server soon where i will try do run the beta.

I've created an issue for the record, will try to see if i can find some time to dig around in code.

Awesome, just need to find some time to re-install my home server for testing ;)

I'm pretty sure this is not the way to get features into PVE ;) The guys at Proxmox are quiet up to date with bleeding edge technologies and are aware of the new release already. Also they stated it will be delivered after testing has shown that it's possible. To keep up the awesome work, just...

RAID0 would be the proper way. And yes, you can't correct checksum...but you also can't with any other filesystem using a single disk. So no real loss.

We're running a lots of servers since years without problems. But please be warned, make sure it's some kind of professional SSD (Datacenter, Server, ...). Normal consumer SSDs wear quickly and PVE is writing a lots of data (logs, transactions, ...). You can search the forum for problems (and...

But ZFS in RAID0 is possible with one disk. And then you'll be able to use all of the fancy ZFS features (snapshots, compression, arc) and not lose something compared to any other filesystem running on a single disk, so yes, if you have plenty of RAM, stick to ZFS.

Awesome. Please keep us posted ;)

I just used really small SSDs just for default ext4 Debian plus Proxmox and when everything was set, I created ZFS on all other disks as extra Pools. This way I have ZFS data disk which I can just plug into a new PVE setup just in case.

Yes, but in this case, the filesystem can get corrupted, because it does not have full controll and access to the disks, so it can't detect (and prevent) bit rot. And scrubbing on raid controller level might interfer with ZFS. Ran into this once, we already had a spare controller ordered, but...

It still is a bad idea. You're not using the features ZFS is offering AND risking a raid controller hardware failure.

https://github.com/morph027/pve-lxc-scripts ;)

- name: update smbios values proxmox_kvm: api_user: "{{ api_user }}" api_password: "{{ api_password }}" api_host: "{{ api_host }}" node: "{{ node }}" name: "{{ name }}" smbios: "uuid=foo-bar" update: yes Basically the command would be something...

https://tompaw.net/proxmox-vm-watchdogs/

Why not directly installing docker on top of the pve host?

Not tried yet ... overlay2 probably?

Probably browser cache, just try ctrl+shift+r for a hard reload

Interested too for my "workstation" :)

Basically your containers are running the host kernel, therefore we're just bind-mounting the host kernel modules into the container (readonly). You'll need to repeat this step after an pve host kernel update.