Recent content by morph027

I've started something similar years ago as a dynamic gitlab runner (example pipeline): https://morph027.gitlab.io/pve-cloud-init-creator/ Quite complex, as custom userdata relies on snippet storage, which is not yet usable via the API (see https://bugzilla.proxmox.com/show_bug.cgi?id=2208)...

Happy new year! Great to hear, wanted to play around and evaluate your hosted PBS since the first announcement. I'm running a pbs for a customer in my basement at home which I want to replace eventually.

Thanks, can confirm this works. This works too ;) Thank you!

Just tried to setup a test mirror with ondrej php ppa and got the following error: # curl -Lo /tmp/ppa-ondrej-php.asc "https://keyserver.ubuntu.com/pks/lookup?op=get&search=0x14aa40ec0831756756d7f66c4f4ea0aae5267a6c" # proxmox-offline-mirror config mirror add --id ppa-ondrej-php...

Chime in, would love this feature too ;) My current workaround: https://gitlab.com/morph027/pve-cloud-init-creator/#snippet-storage

You can at least use cloudinit data from snippets, which can be edited through the webinterface. https://pve.proxmox.com/wiki/Cloud-Init_Support#_custom_cloud_init_configuration

You need to install the module on the host, not in the lxc. Example: https://nixvsevil.com/posts/wireguard-in-proxmox-lxc/

Hm, okay. I'm only using ipxe (as recommended in the README), both for legacy and uefi systems without any errors.

You might want to have a look at https://wiki.x2go.org/doku.php

You can use your own custom cloud init files: https://pve.proxmox.com/wiki/Cloud-Init_Support#_custom_cloud_init_configuration

As I struggled to create a docker machine driver myself, I came up with another idea which I'm using right now to easily bootstrap docker in KVMs: https://gitlab.com/morph027/pve-cloud-init-creator Probably the concept will work for @LnxBil driver too if he finds some time ;)

I don't think so, my servers are all running on ZFS with multiple VM's on this kernel. Is your ZFS running on hard disks or SSDs?

Does it work with the previous kernel? Probably related to C-States: https://forum.proxmox.com/threads/proxmox-ve-5-0-ryzen-7-1700x-crashes-daily.36123/ Got a EPYC 7351P w/ 128GB Memory running the kernel since 22 days without any issues.

Also on my home lab (Intel(R) Xeon(R) CPU E3-1220L V2, 16GB RAM)

Also running cluster of 3 mixed nodes (ZFS) without any problems since the first release. - Intel(R) Xeon(R) CPU E3-1230 v3 w/ 32GB RAM - Intel(R) Xeon(R) CPU E3-1240 v5 w/ 64GB RAM - AMD EPYC 7351P 16-Core Processor w/ 128GB RAM