Search results

I have a cluster with all nodes on ext4 root. I would like to add a few (new) nodes with zfs raid1 root. I found out that there are some issues, and I would like to know what's the best way to proceed: - The local-lvm storage shows up with a "?" on the machine with zfs root, which is...

Yes, that's my understanding, too. I am just hoping that someone may have some piece of knowledge that I don't. :)

Hello, I am planning on using sanoid/syncoid or something similar to perform snapshots and backups of my zfs pool(s). I understand that I can add packages and/or do whatever I need in the host debian environment, but I was wondering if I can do the same inside an lxc container with the host...

Sorry, late response, but I am wondering what you mean by both networks needs to be routed. Does that mean: a). If (let's say) the public network is on subnet A, it can also reach subnet B via subnet A's gateway (ie. reachable) or b). overlay networks, ie. have machines with IP addresses...

I am sure I said "no", since the upgrade(s) asked about other configuration, just not that one. Are there other settings that control config file prompting? I didn't think so..

the conf file is still there, except it's been overwritten. A backup file is created (timesyncd.conf.dpkg-bak) but no user feedback that it occurred. The only way I found out is because ceph complained about some of my nodes having a drifting timestamp. timesyncd is still installed and...

Sorry for not being specific. Details below. What doesn't work: The error I am seeing is: root@vis-ct-clx-08:~# docker run -it centos:7 bash docker: Error response from daemon: cgroups: cgroup mountpoint does not exist: unknown. ERRO[0000] error waiting for container: context canceled...

I spoke too soon. This works on Ubuntu 18.04 LXC containers, but does not work with Ubuntu 20.04 containers. If this was an issue with "old" Centos 7 style containers only, then it definitely would not appear in 20.04.

Hello, I am in the process of upgrading our cluster to Proxmox 7, and came across the following: We have locally edited /etc/systemd/timesyncd.conf to use a local NTP server, since our firewall does not allow external NTP connections. After upgrading to Proxmox 7, the above conf file edits are...

Confirmed. /etc/pve/lxc/*.conf files don't need any editing when moving from Proxmox 6.

@t.lamprecht , is this going to be fixed in an update?

Solution provided in https://forum.proxmox.com/threads/migration-from-6-4-to-7-0.92358/#post-404214. It works for me.

I can confirm that this works. Strangely enough, this also works with docker inside the LXC container.

@t.lamprecht , perhaps you can help here? Thank you!

@t.lamprecht , do you know if changes in /etc/default/grub will disappear after a package update? Thanks! george

Having the same problem. Posted another thread before finding this one (https://forum.proxmox.com/threads/proxmox-7-lxc-cgroup-issue-with-docker.92722/). Also using docker inside LXC, trying to avoid using cgroup2 (for the time being). Funny how the error message is about devices.deny, while...

Ok, I saw some more docs saying that one should add systemd.unified_cgroup_hierarchy=0 to the kernel boot params to revert to original cgroup, but if I do this, I cannot even bring my containers up: root@vis-hsw-00:/etc/pve/lxc# pct start 132 explicitly configured lxc.apparmor.profile overrides...

Upgraded to Proxmox 7, installed has no problems (well, pending issue https://forum.proxmox.com/threads/unknown-video-mode-on-fresh-proxmox-7-install.92623/#post-403828, but that's a different story). We are running LXC containers with docker and gitlab-runner inside them. I modified the...

setting "nomodeset", or for that matter setting "vga=0x0317" work around the issue. Thanks for the hint. I will plugin monitors next time I get in the lab. I agree with you that mga is quite common, but so are Raritan VGA dongles in a server / lab environment. So, if someone does not have a...

On same type of machines, I've installed CentOS 6/7/8, Ubuntu 14/16/18, Windows 10, and Proxmox starting from 5.x upgraded regularly. Proxmox 7 had the same behavior no matter if it was installed via ISO or update. I've also checked all the relevant /sys/class/{drm,graphics,vtconsole} files...