Nice. You you restore often?

How often do you do this?

To me it’s very gimmicky and requires a lot of work. It probably fits English speakers better as I’ve not had any luck using local voice.

The voice focus is fucking el-el-lame

Yeah, just like pounds

Like fingerprinting. Or at least makes it a bit harder to figure out who what and where you are.

That depends on what your error is. It’s not a magic process, it just tries to help you with formatting. The validate is the magic, it helps you spot errors as you make them.

Does it even fucking matter what’s banned in what echo chamber??

Thanks. My setup is way over complicated with 3 hosts in a cluster and shared storage, so local storage on the hosts stay unused. But i have been thinking about redoing it with separate hosts. This solution looks promising for sharing data, even if just on one host

So lxc containers and not vm’s

Could you explain further with a bit more detail? I havnt looked at this in a while but back then the options where virtiofs or nfs

If you want to share storage you need some way of doing that. Zfs is a good option for storage on vm-host level, but ist not designed for shared usage. Im not sure what you are after, but maybe you want zfs storage inside the vm for snapshots, dedup etc? Or maybe you want to share your media storage between vm’s? The first case you can use zfs inside your vm, it does not know or care about how its disks are stored or of they are a physical drive. For the second use-case you want some way to share drives, like smb, nfs etc. or a distributed filesystem if you really want to over complicate things. Truenas might be over overkill for sharing a few volumes, but you need something. I believe you can share zfs over nfs now but i have never used that outside of proxmox cluster storage

I use both debian on a vm with samba+nfs and a bare metal truenas for my needs. Find your needs and figure out what solves them

So you mount the pool to each vm that needs the shared data? Afaik zfs is not made for concurrency

Looks like a tiny screw hole on the top.

Scrap that - after upgrading it went bonkers and will always use one of my «knowledges» no matter what I try. The websearch fails even with ddg as engine. Its aways seemed like the ui was made by unskilled labour, but this is just horrible. 2/10 not recommended

Possibly. Been running it since last summer, but like i say the small models dont do much good for me. I have tried llama3.1 olmo2, deepseek r1 in a few variants, qwen2. Qwen2.5 coder, mistral, codellama, starcoder2, nemotron-mini, llama3.2, qwen2.5-coder, gamma2 and llava.

I use perplexity and mistral as paid, with much better quality. Openwebui is great though, but my hardware is lacking

Edit: saw that my mate is still using it a bit so i’ll update openwebu frpm 0.4 to 0.5.20 for him. Hes a bit anxious about sending data to the cloud so he dont mind the quality

I have the same setup, but its not very usable as my graphics card has 6gb ram. I want one with 20 or 24, as the 6b models are pain and the tiny ones don’t give me much.

Ollama was pretty easy to set up on windows, and its eqsy to download and test the models ollama has available

*Bri’ish

Theres a subscription for this that works kinda like that.

Otherwise a vpn into your hone network gives you access from your devices. Maybe your router already supports this, otherwise tailscale or zerotier and similar can be a good solution.

I dont have issues exposing my ha to the internet through caddy, but i filter traffic based on country of origin (geoip2). Used to have separate auth in front but i removed that a few months ago

Edit: not too much use of running two containers if you expose the same storage to both. Better option would be to have two reverse proxies, one for local and one for internet, both proxyinf the same ha instance. That way you can get ha on normal https port with certs.

Imo you are pretty safe with a reverse proxy with an extra layer of security.

No - i would advocate for not using docker if I need a network interface. But thats my opinion, and others will have a different one.

You can use macvlan networking, and if you need host<->container communication you give your host a macvlan interface instead or in addition to the root nic. Macvlan works “on top of” an existing interface, so theres no routing locally between the underlying nic and the macvlan nics.

If the host have several nic’s you can pass one through to a given container