uek2wooF

I removed all the events and added a path to the config for that container to map a subdir in the zm share to /var/cache/zoneminder and restarted the container. All good.

Oh looks like the majority of the events are from the last week so I guess that why they aren't getting purged yet. So the question remains, how do I make the events write to the array and not to docker.img?

I just tried running DeleteOldEvents manually (by clicking the execute button) and it doesn't seem to be working. I recently rebuilt my entire cache and reinstalled zm, but all my zoneminder settings were still there. I wonder if something is messed up now.

The directory /var/cache/zoneminder/events seems to be writing inside the container and not to the Zoneminder share. Is there a way to map this dir to outside the container? It is 309 gb. Does this mean the DeleteOldEvents filter is not running? Do I need to enable that somehow?

This would be great if you could install to a container instead and get gpu accel like they do with steam-headless. I have installed macos in a container before using this (but I didn't try gpu): https://github.com/sickcodes/Docker-OSX It works really well.

I am setting up a new unraid to replace my existing server. How can I get swag to pull the certs since there nothing is pointing to the new server yet? Or should I just scp them over from the existing unraid?

So if I want to mirror instead of parity how do I do it? I don't see a way to combine the 2 disks in the array.

I am building a new unraid server. I have never understood the point of the super slow parity array and I was thinking of just using one disk for unraid and another for a simple rsync backup. Is the array really better in some way? Like how would you know if a disk died if it is in the array? How would you know if it was the parity disk or not? What would you need to do? You still need backups even with a parity disk so I don't see what it buys you. Why not use a regular mirror or raid instead? In my existing unraid server the disks that are dying are the cache. As far as I know the array is fine although the parity check finds at least one error every time. There needs to be a better way to move the cache onto new disks. The best thing I could come up with was to buy another server and migrate to it long enough to rebuild cache on the old server. I can't even copy VMs off the cache because the disks are in such bad shape. Luckily I was able to save most docker container configs.

When I make my own containers I put them in /mnt/user/appdata which is where all the other containers go when you install them from the apps tab.

I wrote a guide for making your own dockers. Of course they didn't pin it or anything so it takes some searching.

use the swag docker for proxy. there is a spaceinvaderone video for the letsencrypt docker which is the old name for swag

Ok I solved it. For some reason the logs don't actually show the logs. But I got a bash on the docker with docker exec -it deadbeefabc123 bash Then I hoped that the renewal runs out of cron. And it does. So I got the command from there and did /app/le-renew.sh and saw the real error in the output. I don't want to paste it here because it has my IP and domains but basically it was showing an error connecting to the IP I recognized as being the old one. I have a dynamic IP at home (and yes I should set up something to update it in dns). The IP only changes every few years. It changed a few weeks ago and I changed it for some domains and not all since they are on different dns providers. Since LE needs to put a file on the webserver for the domain in order to prove you own it, it couldn't verify I owned those domains anymore. I fixed the IP on my provider for those 2 domains, reran the renew script, and good to go. Whew.

Don't do passthrough, it is just a pain and not worth the hassle, maybe unless you have enough video cards for passthrough and for a head for the box (if no onboard). Although building a streaming gameserver was kind of fun... Only use a mobo with onboard video. So annoying when you have one GPU doing passthrough and no other way to debug things when it won't boot. Even though a mobo supports 8 hard drives, good luck getting the wiring to reach and still be able to put the case covers on. Or at least put them all in at the beginning. Or at least run all the wiring in the beginning if you might add disk later. Adding wiring later on is a huge pain. Don't use NVME ssd. They get super hot, don't live long, and they are hard to access once the machine is built. You want to completely take the machine apart to change a disk? These are just my opinions from my experience. If you disagree do whatever you want.

I fixed the conf files but still have old certs.

updated swag container and now tons of this in the log, this file doesn't exist in /mnt/user/appdata nginx: [emerg] "stream" directive is not allowed here in /etc/nginx/conf.d/stream.conf:3