Naate

joined 9 months ago
[–] Naate@lemmy.world 1 points 4 months ago (1 children)

Interesting. I'll dig a little more then. Most of my vm experience has been on desktop for various reasons, and it's almost always been a pain in the ass and not worth the effort.

I assume the kvm stuff can be running a minimal os, sort of like an alpine docker image?

[–] Naate@lemmy.world 1 points 4 months ago (3 children)

For the most part, this old bucket is doing just fine with probably more than I should be throwing at it.

I'm curious as to why proxmox and VMs over a minimal Debian install with docker containers, though? At least, from my understanding, proxmox would be requiring a lot more hardware overhead when I'm mostly just running emby/jellyfin, nextcloud, homeassistant (and related services) and frigate (with a coral).

It's definitely a lot, but I also rarely see cpu use over 70% (typically much lower), though frigate likes to cause problems occasionally. And I've never seen a concerning amount of ram usage.

Definitely getting one of those little n100s soon, and will probably move the home automation stuff over there, and slowly transition the current box into being a nas and nothing more.

[–] Naate@lemmy.world 6 points 5 months ago

I think you're right. I'm just trapped in the cycle of over-thinking and second guessing my knowledge and capabilities.

 

I'm in the process of planning upgrades for my server, and I'm trying to figure out the "best" drive configuration for Docker. My general understanding would be that the containers should be running from an SSD, and any storage (images, videos, documents) should use a volume on an HDD.

Is it as simple as changing the data-root to point to the SSD, and keep my external volumes on the HDD as defined in my existing compose files? I've already moved data-root once b/c the OverlayFS was chewing up the limited space on the OS drive, so that process isn't daunting.

If there's a better way to configure Docker, I'm open to it, as long as it doesn't require rebuilding everything from scratch.

For reference, the server is running Debian Bookworm on an older i5 3400 with 32GB RAM.

[–] Naate@lemmy.world 3 points 6 months ago

Hehe. This is true.

But there is also a big quality difference between Klingon and languages like German,Spanish, and Japanese.

[–] Naate@lemmy.world 6 points 6 months ago (2 children)

I fell into serious FOMO b/c of some friends joking around about the owl harassing them and then getting into daily xp competitions... so I joined and tried Klingon.

It is very not good. The sentences it builds for learning are...weird at best, and the audio was inconsistent. Maybe it's my learning style conflicting with how Duo does things, but... I hated it.

 

Recently, the lights in my office have been becoming randomly unresponsive, with no change to the setup/environment. They're the only zigbee devices in the mesh that behave this way, and they're also the closest to the gateway.

HA, Z2M, and NodeRed don't show any errors, and the states from the lights/Z2M are toggling, but the bulb itself doesn't do anything. For example, the light is physically on, but HA says it's off. I have to turn the light on in HA, and then when I turn it off the light also turns off.

The bulbs are all Tradfri (one is an RGBW, one standard ccww, the other is a large globe ccww). They are in an HA-defined group and are also controlled by the Adaptive Lighting add-on (other lights controlled by adaptive lighting do not experience this issue)

HA and Z2M are up to date, no firmware updates available for the bulbs, and the controller is a cc2652-stick from Slaesh. Everything is running in Docker on a Debian server. HA is the Container/Core version, not HA OS. The dongle is on a short extension and sits above the server and networking gear.

I'm at a loss as to why these would suddenly begin misbehaving.

Ninja edit: I realized that I did add an aqara 4-button switch in the room recently, but it's not used for those lights. But that's the only change I've made to the zigbee network recently. I'm fairly sure it was added after I noticed this issue, though.