Search results

Thanks @spirit, I added your note to the post.

Here's the "report": https://du.nkel.dev/blog/2022-01-21_proxmox_root_migration/ I am not sure how much value is added with this, because setups may highly vary, but maybe this can serve as a starting point. Let me know if you see anything that should be changed.

Many thanks for the explanations. I want to ask and verify if I understood correctly: The ZFS bug with swap only applies in situations with low space? I have a dedicated ZFS Mirror for rpool with 250GB, and since Proxmox only consumes 5GB, I have 230GB available. That means having 8GB swap on...

I don't - I haven't had the need for shared bind mounts. Have you enabled fuse in the Container Proxmox options (under Features)? The link you gave refers to virtual fuse mounts produced inside the container, linked back to the host. If it is an issue, I think this may not have something to do...

> Sorry, but using XFS ontop of ZFS is not using ZFS. You also did not go to another continent by bicycle if you're sitting on it while flying on a plane. I quote myself: > but it is on lower-end-machines significantly slower than using ZFS directly on the host. I have done extensive...

> So, you're not using the awesome ZFS-Backend for Docker then which is MUCH slower than using ZFS directly and you will not have the cool features like docker image layers in snapshots and automatic datasets for docker volumes. AFAIK it is only slower for building Docker images - which only...

I can confirm that ZFS+Unprivileged LXC + Docker works flawlessly. See here. I have 7 Unprivileged LXC with Docker nested inside each, with a total of about 25 docker containers, running on ZFS Volumes formatted as XFS. No problems since 2 years. Even heavier containers (Gitlab, Nextcloud etc.)...

Thanks for getting back. I did a Restore recently when upgrading from Proxmox 6.4 to 7.1 (because I moved to ZFS, including the Hypervisor itself, which resides on a ZFS Mirror now). I noted down the steps, could share them here. It is not complicated and worked flawlessly. I also expanded my...

Thanks for reporting! Yes, I heard similar reports for this docker-FUSE approach. Which is why I do not use FUSE - everything runs stable with /var/lib/docker on a separate host mount (as describes in the blog post). I haven't actually tested FUSE/fuse-overlayfs myself (primarily because I don't...

Bevorzuge auch diesen weg, da es so einfacher ist Web-Dienste in einer DMZ (Demilitarized Zone, i.e. kein eigenständiger egress traffic) zu betreiben.

Hi timdonovan, thanks for getting back and the kudos. Testing overlay-fs (and adding results to the blog post) is on my list. Currently not super important since I am fine with my setup, but seeing your results pushes my interest. Will try this soon and give an update. Your issue with snapshots...

You are sure this needs to be installed on the Proxmox host? This guide suggests otherwise.

I have update the blog post about Docker and unprivileged LXCs: https://du.nkel.dev/blog/2021-03-25_proxmox_docker/ Tested: - in Proxmox 5.4, 6.4 and 7.1-10 - with Ubuntu (21.10) and Debian (11) LXC Templates - using Directory Storage and ZFS formatted volume mount All of this is working very...

If you restart, ZFS will attempt an automatic resilver. If (by chance), no errors are found, then your zpool will be labeled as fine again. This does not necessarily mean that everything is ok - only if you run a scrub, and if this finished without errors, you know for (pretty) sure that you do...

You won't be able to identify this issue with software alone. Try to replace parts and narrow down the cause. 1. Switch drives to different slots, if you have a backplane. Same errors? Likely not a drive, and not the backplane. Error stays with the same drive(s)? Perhaps it is the drive. 2...

Check dmesg and smartctl --all for CRC errors, which are quite often related to cable or other issues, not the drive. If your long smart test succeeds without error, it would be another hint in that direction. I had quite a number of UDMA CRC Errors due to faulty (and too long) SATA Cable...

I think this is related to performance improvements used by Docker to speed up the use of docker layers in docker build and docker commit commands, which does not seem to work in this specific case with XFS on ZFS (see here, also the docs). At the same time, you should see the following warnings...

This. An example docker-compose.yml that stays in /srv/miniflux/docker-compose.yml in the unpriviliged LXC. I usually create users for each docker-service, e.g.: sudo useradd -r -s /sbin/nologin -m -d /srv/miniflux -U -G docker miniflux sudo -u miniflux -H bash The docker-compose.yml with a...

This is a good question: Firstly, you have ZFS Snapshots - if /var/lib/docker hold important information, then create a Snapshot alongside a LXC backup (or, do both with ZFS Snapshot, the LXC Vol and the /var/lib/docker VOL). If you need files (e.g. for archiving backups), you can send these...

I see the same with Proxmox 7.1-8 and Docker in unprivileged LXCs. I did not notice any issues or performance Problems, usually this is only reported once, when the LXC/Docker starts. All my containers still work. I have /var/lib/docker mounted from a ZVOL (ZFS) that is formatted as XFS.