Search results

Migrated today from Proxmox 6.4 to 7.1-8. I wanted to migrade my Promxox root (Hardware Raid 1) to ZFS Software Raid1 Mirror, so I installed from ISO from scratch. I have 3 Unprivileged LXCs with Docker nested and about 25 Containers. In each of these LXCs, the Docker system directory...

I am not an expert, so make sure you have backups ready before trying suggestions. pct restore 110 /data/dump/vzdump-lxc-100-2022_01_03-12_20_07.tar.zst --rootfs local-lvm:10 Explanation: 110 is the new container ID - it should not be in use --rootfs provides "advanced" instructions to...

This is not ZFS specific. I haven't used lvm, but --rootfs expects information for the new mount point. Check with pvesm status beforehand for the exact name/path, otherwise it will use what is specified in the CT conf. The Proxmox wiki suggests that you can use --rootfs without the mount...

Thank you! I am still on Proxmox 6.4-13, so that is perhaps why I am not able to use Ubuntu 21.10. pveversion > pve-manager/6.4-13/9f411e79 (running kernel: 5.4.151-1-pve)

Happened to me when trying to upgrade from Ubuntu 21.04 to 21.10. lxc-start 108 20220104081607.586 DEBUG conf - conf.c:run_buffer:303 - Script exec /usr/share/lxc/hooks/lxc-pve-prestart-hook 108 lxc pre-start produced output: unsupported Ubuntu version '21.10' Use this quick check to verify...

This was far too complicated. 1. Create a backup 2. Restore the backup with smaller size root disk: pct restore 101 /data/dump/vzdump-lxc-100-2022_01_03-12_20_07.tar.zst --rootfs encrypted_zfs:100 where: 101 is the new CT id (if you want to get it the old one, remove the container first and...

Thanks for the report. There is also another approach/guide. Check this ansible notebook that contains all steps: - create zvol and format with ext4 - mount the drive and chown all files to 100000:100000 with chmod 0711 - can be mounted in docker with overlayfs2 and nesting=1,keyctl=1 enabled...

Please update here with your experiences. Still with Kernel 6.4 due to the unpriviliged LXC/Docker issues.

I use Let's encrypt SSL certs internally, which are retrieved automatically through Acme and DNS API (cloudflare). No need for self-signing (and no need for opening any port). Not sure though if this is your issue.

Ich habe das hier beschrieben. Du brauchst lm-sensors und eine lokale installation von Telegraf. Ich nutze das auch, um Smart HDD auszulesen bzw. meine APC USV. In dem Paket macht das mehr Sinn als nur die Temperaturen über IPMI zu bekommen.

Ich habe ein ähnliches Setup: hauptsächlich freiberuflich bzw. privat, zum testen und lernen, und für self-hosting relevanter Dienste, nur mit 32GB etwas weniger RAM. Allerdings habe ich entgegen der bisherigen posts alles in LXCs (unprivilegiert) und fahre damit seit 2 Jahren sehr gut. Die...

You need to use port 443 and Telegraf. I have this setup with InfluxDB 2.0, but with PVE 6. Here is a short blog post. Your Telegraf config part for submission to InfluxDB2.0 with SSL looks like this: # Configuration for sending metrics to InfluxDB [[outputs.influxdb_v2]] urls =...

Many thanks, I really appreciate the views. Of course, I do and did my own research on btrfs/zfs. I was looking into the pros/cons for over a year now. When coming here, I had a slight favor for zfs, which is now a bit more substantiated. Also found this ansible playbook, which suggests it is at...

Interesting! Many thanks. I wonder why the quoted BTRFS docs suggest that the ZFS Storage driver is not usable inside a container, when the Docker docs actually have a separate section for using the ZFS storage driver, and LXC containers appear to be fully compatible with ZFS.

Now that BTRFS is supported by Proxmox VE 7.0, how would you evaluate the choice for ZFS <-> BTRFS? I currently have: 2x 16TB HDD Raid 1 (Proxmox storage) 2x 256GB SDD Raid 1 (for Hypervisor itself + VM data/temp) 2x 16GB HDD Raid 1 offsite I want to switch to either ZFS or BTRFS to avoid...

Just if anyone finds this useful: In addition to having full tar backups, I like to track changes of important files in git, so I have a full history. Install git. I did this on the host. setup repo with: filelist.txt containing all the files that you want to track, e.g.: # container configs...

Yes, I can run docker stats with the latest versions (proxmox, docker): CONTAINER ID NAME CPU % MEM USAGE / LIMIT MEM % NET I/O BLOCK I/O PIDS 60c58da63f55 docker_invidious_1 0.02% 343.9MiB / 1GiB 33.58% 340MB / 12MB...

As of: - pve-manager/6.4-8 - kernel: 5.4.114-1-pve - Docker version 20.10.7 I still get this error, even with nesting and keyctl enabled. In my case, it was simply removing/commenting hostname from the docker-compose.yml for (in this case) gitlab: web: image: 'gitlab/gitlab-ce:latest'...

This also does not work here (Debian 10 LXC): $ apt install --reinstall --purge locales $ dpkg-reconfigure locales perl: warning: Setting locale failed. perl: warning: Please check that your locale settings: LANGUAGE = (unset), LC_ALL = (unset), LC_CTYPE =...

Did this myself. Here is the answer to: > So should I add corosync.conf to /etc/pve myself? Maybe following the example of MRosu's post on Mar 6, 2017? This is the case if there is no cluster in proxmox. Check in the UI under Datacenter > Cluster. If this is empty, you only need to edit...