Search results

Looks like ZFS takes a dedicated pool, so that's a no-go. VFS is called out as do not use as it causes poor performance. On the previous kernel, what would it have used? That was performant enough for my needs.

I assume this is why it just showed up.... From the docker filesystem docs. "The Docker Engine has a prioritized list of which storage driver to use if no storage driver is explicitly configured, assuming that the storage driver meets the prerequisites, and automatically selects a compatible...

Is that vfs? Don't see a "vs".

That's interesting, so that same compose yaml I've been using for over a year with no problems. That being the case, any ideas why after this new kernel update it would stop working? I have about 30 containers that work together to form my media setup, and since I can no longer load them, I'm...

Can you see if you can get this to run with Compose? For me, it won't even complete the build, error's out before it can. version: '2' services: cloudflare-ddns: image: oznu/cloudflare-ddns:latest restart: always environment: - API_KEY=<REDACTED> - ZONE=<REDACTED>...

On it, just FYI, the guests that are having trouble with many of my compose yaml's can run hello world without any issues. I'll go through the process regardless.

Looking over the guest journal I cleaned up a few things checkmk mainly, we can ignore the directory not found as well, cleaned that up too, old configs.

I've been running this way for a few years without issues, so as much as it may be discouraged, it hasn't been a problem before today. To answer your questions: Here's an example of a container that loads without any issues. version: "3.1" services: audiobookshelf: image...

Didn't upgrade the containers themselves today, here's what was upgraded on the hosts. Everything worked before, not so much after. Install: pve-kernel-5.15.83-1-pve:amd64 (5.15.83-1, automatic), pve-headers-5.15.83-1-pve:amd64 (5.15.83-1, automatic) Upgrade: pve-firmware:amd64 (3.6-1, 3.6-2)...

Hi All, EDIT: Here's the fix, it's clean for most setups, things like Home Assistant OS may or may not work, still finding out. Ultimately, you'll need to create a file in /etc/docker/ called daemon.json. Inside the file put a line: storage-driver": "vfs" This will restore your old...

Ah, control-F5 did it. Browser cache was hiding it from me! :) Thank you! Keith

Hello, I was backing up my hosts on a regular-basis, and it seems the backup/pruning system has recently changed. I want to be sure I'm following the updated protocol. Likewise, I believe it's just a matter of refining my shell script. Here's what I used to use (note, some of my variables...

I'm going to recant, I do still have one issue, although it's no longer crashing when I reboot a guest container it still isn't autobooting any containers with the configuration for NVIDIA in the container. So, something is still not quite right. I also noted that when I check the kernel...

Cool. My post showed back up! :) So, since my last post I've pinned the kernel at 5.13.19-6-pve and the issues went away. I know the community code is considered unstable, yet there seems to be some sort of bug in the latest releases. Would you still be interested in the syslog? I can...

I posted a thread in regard to current issues with my Proxmox implementation. I see in my profile that I have a reward for a “first post”, yet the thread is gone. Can one of the admins please restore it? Sorry I'm posting here, I don't see a manner whereas I can message the mods directly...

Hey all! I am on the latest upgrades to the community edition of Proxmox. I have been running just fine for quite some time, yet now all of a sudden I'm having a major issue. I have 3 containers that need to access my NVIDIA GPU. They're configured like this: ----- arch: amd64 cores: 6...